@pnpm/lifecycle
Package lifecycle hook runner
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 to GitHub Actions CI/CD publishing; SLSA provenance attestation confirms builds originate from the official pnpm/pnpm repo. This transition is stable going forward. | ai | |
| provenance | no-provenance | AI (provenance): Established pnpm monorepo package with strong publisher track record; lack of provenance is consistent across all versions and not a meaningful risk signal here. | ai | |
| dependencies | unvetted-dep:@pnpm/npm-lifecycle | AI (dependencies): @pnpm/npm-lifecycle is a sibling package within the official pnpm monorepo; this dependency relationship is stable and expected across all versions of @pnpm/lifecycle. | ai | |
| provenance | slsa-provenance | AI (provenance): pnpm publishes via GitHub Actions with SLSA provenance; this is expected and stable for all @pnpm/* packages. | ai | |
| phantom-deps | phantom-dep:path-exists | AI (phantom-deps): path-exists is a declared runtime dependency in package.json; phantom detection is a false positive for this package. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 1001.0.38 | 12 / 9 | |
| 1001.0.37 | 12 / 9 | |
| 1001.0.36 | 12 / 9 | |
| 1001.0.35 | 12 / 9 | |
| 1001.0.34 | 12 / 9 | |
| 1001.0.33 | 12 / 9 | |
| 1001.0.32 | 12 / 9 | |
| 1001.0.31 | 12 / 9 | |
| 1001.0.30 | 12 / 9 | |
| 1001.0.29 | 12 / 9 | |
| 1001.0.28 | 12 / 9 | |
| 1001.0.27 | 12 / 9 | |
| 1001.0.26 | 12 / 9 | |
| 1001.0.13 | 12 / 10 |
v1001.0.38
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1001.0.37
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1001.0.36
2 findingsThis version was published by a different npm account than previous versions on 2026-02-23. 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.
v1001.0.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1001.0.34
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1001.0.33
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1001.0.32
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1001.0.31
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1001.0.30
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1001.0.29
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1001.0.28
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1001.0.27
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1001.0.26
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1001.0.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.