@pnpm/npm-resolver
Resolver for npm-hosted packages
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): pnpm monorepo migrated from personal account (zkochan) to GitHub Actions CI publishing, confirmed by SLSA provenance attestation. This transition is expected and legitimate for this package. | ai | |
| provenance | no-provenance | AI (provenance): pnpm monorepo packages consistently publish without Sigstore provenance; this is stable for the entire @pnpm/* ecosystem. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 1005.2.5 | 29 / 11 | |
| 1005.2.4 | 29 / 11 | |
| 1005.2.3 | 29 / 11 | |
| 1005.2.2 | 29 / 11 | |
| 1005.2.1 | 29 / 11 | |
| 1005.2.0 | 29 / 11 | |
| 1005.1.2 | 29 / 11 | |
| 1005.1.1 | 29 / 11 | |
| 1005.1.0 | 29 / 11 | |
| 1005.0.2 | 29 / 11 | |
| 1005.0.1 | 29 / 11 | |
| 1005.0.0 | 29 / 11 | |
| 1004.6.2 | 29 / 11 | |
| 1004.6.1 | 29 / 11 | |
| 1004.6.0 | 29 / 11 | |
| 1004.5.0 | 29 / 10 | |
| 1004.4.1 | 29 / 10 |
v1005.2.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1005.2.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1005.2.3
2 findingsThis version was published by a different npm account than previous versions on 2026-03-24. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1005.2.2
2 findingsThis version was published by a different npm account than previous versions on 2026-03-07. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1005.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1005.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1005.1.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1005.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1005.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1005.0.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1005.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1005.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1004.6.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1004.6.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1004.6.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1004.5.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1004.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.