scanoss
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:build/module/cli/commands/helpers.spec.js | AI (source-diff): File is a readable TypeScript test spec; long-line trigger is a false positive for this package. | ai | |
| dependencies | unvetted-dep:sort-paths | AI (dependencies): Legitimate path-sorting utility; stable dependency for this package. | ai | |
| dependencies | unvetted-dep:syswide-cas | AI (dependencies): Legitimate CA certificate utility; stable dependency for this package. | ai | |
| dependencies | unvetted-dep:libarchive.js | AI (dependencies): Legitimate archive library; stable dependency for this package. | ai | |
| dependencies | unvetted-dep:packageurl-js | AI (dependencies): Legitimate package URL utility; stable dependency for this package. | ai | |
| phantom-deps | phantom-dep:syswide-cas | AI (phantom-deps): Declared dep used indirectly; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:gunzip-maybe | AI (phantom-deps): Declared dep used indirectly in archive pipeline; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:tar-stream | AI (phantom-deps): Declared dep used indirectly in archive pipeline; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:sort-paths | AI (phantom-deps): Declared dep used indirectly in this scan tooling; stable false positive for this package. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 0.40.1 | 22 / 19 | |
| 0.40.0 | 22 / 19 | |
| 0.39.0 | 22 / 19 | |
| 0.32.0 | 22 / 19 | |
| 0.22.0 | 20 / 18 | |
| 0.20.0 | 20 / 18 | |
| 0.19.0 | 20 / 18 | |
| 0.17.3 | 20 / 18 | |
| 0.17.0 | 20 / 18 | |
| 0.16.3 | 20 / 18 |
v0.40.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.40.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.32.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.