+1
-1
| { | ||
| "name": "snync", | ||
| "version": "1.3.1", | ||
| "version": "1.3.2", | ||
| "description": "Mitigate security concerns of Dependency Confusion supply chain security risks", | ||
@@ -5,0 +5,0 @@ "type": "module", |
+16
-0
@@ -53,2 +53,18 @@ | ||
| ## Logic flow | ||
| How does snync work from decision tree perspective? | ||
| ``` | ||
| 1. Get "all dependencies" in `package.json` (note, refers to direct dependencies only, not transitive) | ||
| ['dependencies'] and ['devDependencies] | ||
| 2. If a package includes a scope (such as prefixed with a `@snyk/`) | ||
| then remove it from the "all dependencies" list and save it for later, to warn the user to ensure they own that scope | ||
| 3. Foreach of the "all dependencies" gathered, get the time it was introduced to the source-code (i.e. the time it was added to `package.json`) | ||
| 4. Foreach of the "all dependencies" gathered, get the time it was created in the npmjs registry | ||
| 5. Compare the two timestamps | ||
| 5.1. if a package is not found in the registry then signal an error to let them know that this public namespace is not taken, and is vulnerable for someone to employ a Dependency Confusion on them. | ||
| 5.2. if a package is found in the registry, and it was created after the time it was introduced to source-code, then signal a warning that there is potentially an attack in progress and to warn the user to review the premise and legitimacy of that package that exits in the public registry. | ||
| ``` | ||
| ## Supported ecosystems | ||
@@ -55,0 +71,0 @@ |
Shell access
Supply chain riskThis module accesses the system shell. Accessing the system shell increases the risk of executing arbitrary code.
Found 1 instance in 1 package
Filesystem access
Supply chain riskAccesses the file system, and could potentially read sensitive data.
Found 1 instance in 1 package
Shell access
Supply chain riskThis module accesses the system shell. Accessing the system shell increases the risk of executing arbitrary code.
Found 1 instance in 1 package
Filesystem access
Supply chain riskAccesses the file system, and could potentially read sensitive data.
Found 1 instance in 1 package
21076
5.91%103
18.39%