@pnpm/write-project-manifest
Write a project manifest (called package.json in most cases)
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 | no-provenance | AI (provenance): Official pnpm monorepo package published by the trusted pnpmuser account; lack of provenance is consistent across all pnpm packages and not a risk signal here. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 1000.0.17 | 5 / 3 | |
| 1000.0.16 | 5 / 3 | |
| 1000.0.15 | 5 / 3 | |
| 1000.0.14 | 5 / 3 | |
| 1000.0.13 | 5 / 3 | |
| 1000.0.12 | 5 / 3 | |
| 1000.0.11 | 5 / 3 | |
| 1000.0.10 | 5 / 3 | |
| 1000.0.9 | 5 / 3 | |
| 1000.0.8 | 5 / 3 | |
| 1000.0.7 | 5 / 3 | |
| 1000.0.6 | 5 / 3 | |
| 1000.0.5 | 5 / 3 | |
| 1000.0.4 | 5 / 3 | |
| 1000.0.3 | 5 / 3 | |
| 1000.0.2 | 5 / 3 | |
| 1000.0.1 | 5 / 3 | |
| 1000.0.0 | 5 / 3 |
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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1000.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1000.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1000.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1000.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1000.0.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.
v1000.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.