@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 — the axios compromise (March 2026) relied on exactly this gap.
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 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 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 |
v1000.0.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1000.0.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1000.0.32
2 findingsThis version was published by a different npm account than previous versions on 2026-03-07. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1000.0.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1000.0.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1000.0.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1000.0.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1000.0.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1000.0.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1000.0.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1000.0.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1000.0.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1000.0.22
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.21
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.20
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2025-10-21. This could indicate a legitimate maintainer transition or an account compromise.
v1000.0.19
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2025-09-29. This could indicate a legitimate maintainer transition or an account compromise.
v1000.0.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1000.0.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1000.0.16
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.15
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.14
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.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.