snyk-nodejs-lockfile-parser
Generate a dep tree given a lockfile
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Snyk-owned package moving to CircleCI CI publishing; benign maintainer/pipeline transition. | ai | |
| dependencies | unvetted-dep:snyk-config | AI (dependencies): Snyk-owned dependency consistent with this package's ecosystem; stable pattern across versions. | ai | |
| dependencies | unvetted-dep:@snyk/graphlib | AI (dependencies): Snyk-scoped package used for dependency graph parsing; expected dependency for this package. | ai | |
| dependencies | unvetted-dep:dependency-path | AI (dependencies): Well-known utility for lockfile parsing; appropriate for this package's purpose. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Legitimate Snyk utility library; README linking to GitHub is not a link farm pattern for this package. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is declared as a runtime dependency in package.json; phantom-dep is a false positive here. | ai |
Versions (showing 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 2.9.1 | 18 / 15 | |
| 2.9.0 | 18 / 15 | |
| 2.8.1 | 18 / 15 | |
| 2.8.0 | 18 / 15 | |
| 2.7.1 | 18 / 15 | |
| 2.7.0 | 18 / 15 | |
| 2.6.1 | 18 / 15 | |
| 2.6.0 | 18 / 15 | |
| 2.5.1 | 18 / 15 | |
| 2.5.0 | 18 / 15 | |
| 2.4.5 | 18 / 15 | |
| 2.4.4 | 18 / 15 | |
| 2.4.3 | 18 / 15 | |
| 2.4.2 | 18 / 15 | |
| 2.4.1 | 18 / 15 | |
| 2.4.0 | 18 / 15 | |
| 2.3.3 | 18 / 15 | |
| 2.3.2 | 18 / 15 | |
| 2.3.1 | 18 / 15 | |
| 2.3.0 | 18 / 15 | |
| 2.2.4 | 18 / 15 | |
| 2.2.3 | 18 / 15 | |
| 2.2.2 | 18 / 14 | |
| 2.2.1 | 18 / 14 | |
| 2.2.0 | 18 / 14 | |
| 2.1.0 | 18 / 14 | |
| 2.0.1 | 18 / 14 |
v2.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.0
2 findingsThis version was published by a different npm account than previous versions on 2026-06-25. 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.8.1
2 findingsThis version was published by a different npm account than previous versions on 2026-06-16. 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.8.0
2 findingsThis version was published by a different npm account than previous versions on 2026-06-04. 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.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.