@pnpm/config.deps-installer
Installer for configurational dependencies
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 org's established publishing account (1435 days old, 102 approved packages). Transition from zkochan (creator's personal account) to pnpmuser is a known org-level publishing pattern, not a takeover. | ai | |
| provenance | no-provenance | AI (provenance): pnpm monorepo packages published by zkochan consistently lack Sigstore provenance; this is a stable pattern for this publisher/ecosystem, not a risk indicator. | ai |
Versions (showing 39 of 39)
| Version | Deps | Published |
|---|---|---|
| 1000.1.9 | 16 / 8 | |
| 1000.1.8 | 14 / 6 | |
| 1000.1.7 | 14 / 6 | |
| 1000.1.6 | 14 / 6 | |
| 1000.1.5 | 14 / 6 | |
| 1000.1.4 | 14 / 6 | |
| 1000.1.3 | 14 / 6 | |
| 1000.1.2 | 14 / 6 | |
| 1000.1.1 | 14 / 6 | |
| 1000.1.0 | 14 / 6 | |
| 1000.0.28 | 14 / 6 | |
| 1000.0.27 | 14 / 6 | |
| 1000.0.26 | 14 / 6 | |
| 1000.0.25 | 14 / 6 | |
| 1000.0.24 | 14 / 6 | |
| 1000.0.23 | 14 / 6 | |
| 1000.0.22 | 14 / 6 | |
| 1000.0.21 | 14 / 6 | |
| 1000.0.20 | 14 / 6 | |
| 1000.0.19 | 14 / 6 | |
| 1000.0.18 | 14 / 6 | |
| 1000.0.17 | 14 / 6 | |
| 1000.0.16 | 14 / 6 | |
| 1000.0.15 | 14 / 6 | |
| 1000.0.14 | 14 / 6 | |
| 1000.0.13 | 14 / 6 | |
| 1000.0.12 | 14 / 6 | |
| 1000.0.11 | 14 / 6 | |
| 1000.0.10 | 14 / 6 | |
| 1000.0.9 | 14 / 6 | |
| 1000.0.8 | 14 / 6 | |
| 1000.0.7 | 14 / 6 | |
| 1000.0.6 | 14 / 6 | |
| 1000.0.5 | 14 / 6 | |
| 1000.0.4 | 14 / 6 | |
| 1000.0.3 | 14 / 6 | |
| 1000.0.2 | 14 / 6 | |
| 1000.0.1 | 14 / 6 | |
| 1000.0.0 | 14 / 6 |
v1000.1.9
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.