@pnpm/lockfile.settings-checker
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 canonical pnpm maintainer; transition from pnpmuser org account to personal account is expected for this package family. | ai | |
| dependencies | unvetted-dep:@pnpm/lockfile.verification | AI (dependencies): Sibling pnpm monorepo package; unvetted status is a pipeline artifact, not a real risk. | ai | |
| dependencies | unvetted-dep:@pnpm/config.parse-overrides | AI (dependencies): Sibling pnpm monorepo package; unvetted status is a pipeline artifact, not a real risk. | ai |
Versions (showing 31 of 31)
| Version | Deps | Published |
|---|---|---|
| 1100.0.15 | 7 / 3 | |
| 1100.0.14 | 7 / 3 | |
| 1100.0.13 | 7 / 3 | |
| 1100.0.12 | 7 / 3 | |
| 1100.0.11 | 7 / 3 | |
| 1100.0.10 | 7 / 3 | |
| 1100.0.9 | 7 / 3 | |
| 1100.0.8 | 7 / 3 | |
| 1100.0.7 | 7 / 3 | |
| 1100.0.6 | 7 / 3 | |
| 1100.0.5 | 7 / 3 | |
| 1100.0.4 | 7 / 3 | |
| 1100.0.3 | 7 / 3 | |
| 1100.0.2 | 7 / 3 | |
| 1100.0.1 | 7 / 3 | |
| 1100.0.0 | 7 / 3 | |
| 1001.1.0 | 7 / 3 | |
| 1001.0.30 | 7 / 3 | |
| 1001.0.29 | 7 / 3 | |
| 1001.0.28 | 7 / 3 | |
| 1001.0.27 | 7 / 3 | |
| 1001.0.26 | 7 / 3 | |
| 1001.0.25 | 7 / 3 | |
| 1001.0.24 | 7 / 3 | |
| 1001.0.23 | 7 / 3 | |
| 1001.0.22 | 7 / 3 | |
| 1001.0.21 | 7 / 3 | |
| 1001.0.20 | 7 / 3 | |
| 1001.0.19 | 5 / 3 | |
| 1001.0.18 | 5 / 3 | |
| 1001.0.17 | 5 / 3 |
v1100.0.15
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1100.0.14
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1100.0.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1100.0.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
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.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.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1001.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.0.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.0.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.0.28
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.
v1001.0.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.0.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.0.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.0.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.0.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1001.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1001.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.