@pnpm/lifecycle
Package lifecycle hook runner
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
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 39 of 39)
| 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.25 | 12 / 9 | |
| 1001.0.24 | 12 / 9 | |
| 1001.0.23 | 12 / 9 | |
| 1001.0.22 | 12 / 9 | |
| 1001.0.21 | 12 / 9 | |
| 1001.0.20 | 12 / 9 | |
| 1001.0.19 | 12 / 9 | |
| 1001.0.18 | 12 / 9 | |
| 1001.0.17 | 12 / 9 | |
| 1001.0.16 | 12 / 10 | |
| 1001.0.15 | 12 / 10 | |
| 1001.0.14 | 12 / 10 | |
| 1001.0.13 | 12 / 10 | |
| 1001.0.12 | 12 / 10 | |
| 1001.0.11 | 12 / 10 | |
| 1001.0.10 | 12 / 10 | |
| 1001.0.9 | 12 / 10 | |
| 1001.0.8 | 12 / 10 | |
| 1001.0.7 | 12 / 10 | |
| 1001.0.6 | 12 / 10 | |
| 1001.0.5 | 12 / 10 | |
| 1001.0.4 | 11 / 9 | |
| 1001.0.3 | 11 / 9 | |
| 1001.0.2 | 11 / 9 | |
| 1001.0.1 | 11 / 9 | |
| 1001.0.0 | 11 / 9 |
v1001.0.25
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (pnpmuser) than the most recent previously approved version (zkochan) on 2025-10-21, but pnpmuser is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1001.0.24
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (pnpmuser) than the most recent previously approved version (zkochan) on 2025-10-14, but pnpmuser is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1001.0.23
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (zkochan) than the most recent previously approved version (pnpmuser) on 2025-09-29, but zkochan is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1001.0.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.0.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.0.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.0.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.0.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.0.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.0.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.