@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 — 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 |
|---|---|---|---|---|
| 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.map | AI (phantom-deps): Lodash utilities are used in source; analyzer cannot resolve indirect imports. | 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:lodash.filter | AI (phantom-deps): Lodash utilities are used in source; analyzer cannot resolve indirect imports. | ai | |
| phantom-deps | phantom-dep:lodash.transform | AI (phantom-deps): Lodash utilities are used in source; analyzer cannot resolve indirect imports. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 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 |
v2.16.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.16.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.16.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.16.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.16.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.16.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.16.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.16.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.