@snyk/dep-graph
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): CI/CD publish transition on established first-party Snyk package; no code changes. | ai | |
| phantom-deps | phantom-dep:packageurl-js | AI (phantom-deps): Bundled dist has no scannable imports; legit dep of this Snyk library. | ai | |
| phantom-deps | phantom-dep:lodash.clone | AI (phantom-deps): Lodash utilities are used in source; analyzer cannot resolve indirect imports. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is implicit TypeScript dependency; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:lodash.transform | AI (phantom-deps): Lodash utilities are used in source; analyzer cannot resolve indirect imports. | ai | |
| phantom-deps | phantom-dep:lodash.filter | AI (phantom-deps): Lodash utilities are used in source; analyzer cannot resolve indirect imports. | ai | |
| phantom-deps | phantom-dep:lodash.map | AI (phantom-deps): Lodash utilities are used in source; analyzer cannot resolve indirect imports. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 2.16.11 | 19 / 15 | |
| 2.16.10 | 19 / 15 | |
| 2.16.9 | 19 / 15 | |
| 2.16.8 | 19 / 15 | |
| 2.16.7 | 19 / 15 | |
| 2.16.6 | 19 / 15 | |
| 2.16.5 | 19 / 15 | |
| 2.16.4 | 19 / 15 | |
| 2.16.3 | 19 / 15 | |
| 2.16.2 | 19 / 15 | |
| 2.16.1 | 19 / 15 | |
| 2.16.0 | 19 / 15 | |
| 2.15.0 | 19 / 15 | |
| 2.14.0 | 19 / 15 | |
| 2.13.0 | 19 / 15 | |
| 2.12.1 | 19 / 15 | |
| 2.12.0 | 19 / 15 | |
| 2.11.0 | 19 / 15 | |
| 2.10.0 | 19 / 15 | |
| 2.9.1 | 19 / 15 | |
| 2.9.0 | 19 / 15 |
v2.16.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.16.10
2 findingsThis version was published by a different npm account than previous versions on 2026-07-23. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.16.9
2 findingsThis version was published by a different npm account than previous versions on 2026-06-01. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.