@pnpm/lockfile.utils
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy reflects pnpm major version cadence; SLSA provenance and official pnpm org confirm legitimacy. | ai | |
| phantom-deps | phantom-dep:ramda | AI (phantom-deps): ramda is aliased via npm: protocol to @pnpm/ramda; phantom-dep heuristic misfires on aliased deps. | ai | |
| phantom-deps | phantom-dep:@pnpm/error | AI (phantom-deps): Same-org dep; phantom-dep heuristic unreliable for re-exported or transitively used types. | ai | |
| phantom-deps | phantom-dep:@pnpm/hooks.types | AI (phantom-deps): Types-only dep from same org; not directly imported in JS but used for type declarations. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 1100.0.11 | 8 / 6 | |
| 1100.0.10 | 8 / 6 | |
| 1100.0.9 | 8 / 6 | |
| 1100.0.8 | 8 / 6 | |
| 1100.0.7 | 8 / 6 | |
| 1100.0.6 | 8 / 6 | |
| 1100.0.5 | 8 / 6 | |
| 1100.0.4 | 9 / 6 | |
| 1100.0.3 | 9 / 5 | |
| 1100.0.2 | 9 / 5 | |
| 1100.0.1 | 9 / 5 | |
| 1100.0.0 | 9 / 5 | |
| 1004.0.3 | 7 / 5 | |
| 1004.0.2 | 7 / 5 | |
| 1004.0.1 | 7 / 5 | |
| 1004.0.0 | 7 / 5 | |
| 1003.0.9 | 7 / 5 | |
| 1003.0.8 | 7 / 5 | |
| 1003.0.7 | 7 / 5 | |
| 1003.0.6 | 7 / 5 | |
| 1003.0.5 | 7 / 5 | |
| 1003.0.4 | 7 / 5 |
v1100.0.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1100.0.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1100.0.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1100.0.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1100.0.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1100.0.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1100.0.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1100.0.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1100.0.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1004.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1004.0.2
2 findingsThis version was published by a different npm account than previous versions on 2026-02-17. 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.
v1004.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1004.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1003.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1003.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1003.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1003.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1003.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1003.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.