@pnpm/local-resolver
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): zkochan is the original pnpm maintainer; transition from pnpmuser back to zkochan is expected and legitimate. | ai | |
| dependencies | unvetted-dep:@pnpm/crypto.hash | AI (dependencies): First-party @pnpm/* internal dependency from the pnpm monorepo; unvetted status reflects review pipeline lag, not a security concern. | ai | |
| dependencies | unvetted-dep:@pnpm/read-project-manifest | AI (dependencies): First-party @pnpm/* internal dependency from the pnpm monorepo; unvetted status reflects review pipeline lag, not a security concern. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 1002.1.14 | 6 / 3 | |
| 1002.1.13 | 6 / 3 | |
| 1002.1.11 | 6 / 3 | |
| 1002.1.10 | 6 / 3 | |
| 1002.1.9 | 6 / 3 | |
| 1002.1.8 | 6 / 3 | |
| 1002.1.7 | 6 / 3 | |
| 1002.1.6 | 6 / 3 | |
| 1002.1.5 | 6 / 3 | |
| 1002.1.4 | 6 / 3 | |
| 1002.1.3 | 6 / 3 | |
| 1002.1.2 | 6 / 3 | |
| 1002.1.1 | 6 / 3 | |
| 1002.1.0 | 6 / 3 | |
| 1002.0.2 | 6 / 3 | |
| 1002.0.1 | 6 / 3 | |
| 1002.0.0 | 6 / 3 |
v1002.1.14
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1002.1.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1002.1.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1002.1.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1002.1.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1002.1.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1002.1.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1002.1.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1002.1.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1002.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1002.1.3
2 findingsThis version was published by a different npm account than previous versions on 2025-09-29. 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.
v1002.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1002.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1002.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1002.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1002.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1002.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.