← Home

snyk-nodejs-lockfile-parser

npm Repository Homepage

Generate a dep tree given a lockfile

11
Versions
Apache-2.0
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

snyk-admin

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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 11 of 11)

Version Deps Published
2.7.1 18 / 15
2.6.0 18 / 15
2.5.1 18 / 15
2.4.3 18 / 15
2.4.2 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.0.1 18 / 14

v2.7.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.6.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.5.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.4.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.4.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.4.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.3.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.3.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.3.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.3.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.