@pnpm/create-cafs-store
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): pnpmuser is the pnpm project's shared org publishing account with 105 approved packages; transition from zkochan to pnpmuser is a documented legitimate handoff for the pnpm monorepo. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy explained by publisher transition to shared pnpm org account; no suspicious code changes introduced; part of the well-known pnpm monorepo. | ai | |
| phantom-deps | phantom-dep:@pnpm/fetcher-base | AI (phantom-deps): Same @pnpm scope, listed as a direct dependency; indirect usage patterns in monorepo packages commonly trigger this false positive. | ai | |
| phantom-deps | phantom-dep:@pnpm/exec.pkg-requires-build | AI (phantom-deps): Same @pnpm scope, listed as a direct dependency; indirect usage patterns in monorepo packages commonly trigger this false positive. | ai | |
| provenance | no-provenance | AI (provenance): Established pnpm monorepo package published by the primary pnpm maintainer; lack of provenance is consistent across all pnpm packages and not a risk signal here. | ai |
Versions (showing 36 of 36)
| Version | Deps | Published |
|---|---|---|
| 1000.0.35 | 8 / 5 | |
| 1000.0.34 | 8 / 5 | |
| 1000.0.33 | 8 / 5 | |
| 1000.0.32 | 8 / 5 | |
| 1000.0.31 | 8 / 5 | |
| 1000.0.30 | 8 / 5 | |
| 1000.0.29 | 8 / 5 | |
| 1000.0.28 | 8 / 5 | |
| 1000.0.27 | 8 / 5 | |
| 1000.0.26 | 8 / 5 | |
| 1000.0.25 | 8 / 5 | |
| 1000.0.24 | 8 / 5 | |
| 1000.0.23 | 8 / 5 | |
| 1000.0.22 | 8 / 5 | |
| 1000.0.21 | 8 / 5 | |
| 1000.0.20 | 8 / 5 | |
| 1000.0.19 | 8 / 5 | |
| 1000.0.18 | 8 / 5 | |
| 1000.0.17 | 8 / 5 | |
| 1000.0.16 | 8 / 5 | |
| 1000.0.15 | 8 / 5 | |
| 1000.0.14 | 8 / 5 | |
| 1000.0.13 | 8 / 5 | |
| 1000.0.12 | 8 / 5 | |
| 1000.0.11 | 8 / 5 | |
| 1000.0.10 | 8 / 5 | |
| 1000.0.9 | 8 / 5 | |
| 1000.0.8 | 8 / 5 | |
| 1000.0.7 | 8 / 5 | |
| 1000.0.6 | 8 / 5 | |
| 1000.0.5 | 8 / 5 | |
| 1000.0.4 | 8 / 5 | |
| 1000.0.3 | 8 / 5 | |
| 1000.0.2 | 8 / 5 | |
| 1000.0.1 | 8 / 5 | |
| 1000.0.0 | 8 / 5 |
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 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. Consider requesting the maintainer enable provenance via CI/CD.
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.