@pnpm/prepare
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 author and a highly trusted publisher; transition from pnpmuser to zkochan is expected. | ai | |
| dependencies | unvetted-dep:write-json5-file | AI (dependencies): write-json5-file is a benign JSON5 writer; stable dependency in pnpm ecosystem across versions. | ai | |
| provenance | no-provenance | AI (provenance): pnpm packages consistently lack provenance attestation; stable pattern across 118 versions. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Internal pnpm monorepo utility; missing description is consistent across versions and not a malice indicator. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 1100.0.11 | 6 / 2 | |
| 1100.0.10 | 6 / 2 | |
| 1100.0.9 | 6 / 2 | |
| 1100.0.8 | 6 / 2 | |
| 1100.0.7 | 6 / 2 | |
| 1100.0.6 | 6 / 2 | |
| 1100.0.5 | 6 / 2 | |
| 1100.0.4 | 6 / 2 | |
| 1100.0.3 | 6 / 2 | |
| 1100.0.2 | 6 / 2 | |
| 1100.0.1 | 6 / 2 | |
| 1100.0.0 | 6 / 2 | |
| 1000.0.16 | 6 / 2 | |
| 1000.0.15 | 6 / 2 | |
| 1000.0.14 | 6 / 2 | |
| 1000.0.13 | 6 / 2 | |
| 1000.0.12 | 6 / 2 | |
| 1000.0.11 | 6 / 2 | |
| 1000.0.10 | 6 / 2 | |
| 1000.0.9 | 6 / 2 | |
| 1000.0.8 | 6 / 2 | |
| 1000.0.7 | 6 / 2 | |
| 1000.0.6 | 6 / 2 | |
| 1000.0.5 | 6 / 2 |
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.
v1100.0.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1100.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1100.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1000.0.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1000.0.15
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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1000.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1000.0.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1000.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1000.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1000.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1000.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1000.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1000.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1000.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1000.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.