@pnpm/directory-fetcher
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): zkochan is the original creator of pnpm; the switch from pnpmuser (CI bot) back to zkochan is a legitimate maintainer transition, not a compromise. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy is from zkochan's account perspective only; pnpm project used pnpmuser for automated publishing. zkochan resuming direct publishing is expected for this ecosystem. | ai | |
| provenance | no-provenance | AI (provenance): pnpm monorepo packages are published by the established pnpmuser publisher without Sigstore provenance; this is consistent across all their releases and not a security concern. | ai | |
| phantom-deps | phantom-dep:@pnpm/resolver-base | AI (phantom-deps): @pnpm/resolver-base is declared in dependencies in package.json; phantom-dep finding is a false positive for this package's usage pattern. | ai |
Versions (showing 33 of 33)
| Version | Deps | Published |
|---|---|---|
| 1000.1.26 | 6 / 5 | |
| 1000.1.25 | 6 / 5 | |
| 1000.1.24 | 6 / 5 | |
| 1000.1.23 | 6 / 5 | |
| 1000.1.22 | 6 / 5 | |
| 1000.1.21 | 6 / 5 | |
| 1000.1.20 | 6 / 5 | |
| 1000.1.19 | 6 / 5 | |
| 1000.1.18 | 6 / 5 | |
| 1000.1.17 | 6 / 5 | |
| 1000.1.16 | 6 / 5 | |
| 1000.1.15 | 6 / 5 | |
| 1000.1.14 | 6 / 5 | |
| 1000.1.13 | 6 / 5 | |
| 1000.1.12 | 6 / 5 | |
| 1000.1.11 | 6 / 5 | |
| 1000.1.10 | 6 / 4 | |
| 1000.1.9 | 6 / 4 | |
| 1000.1.8 | 6 / 4 | |
| 1000.1.7 | 6 / 4 | |
| 1000.1.6 | 6 / 4 | |
| 1000.1.5 | 6 / 4 | |
| 1000.1.4 | 6 / 4 | |
| 1000.1.3 | 6 / 4 | |
| 1000.1.2 | 6 / 4 | |
| 1000.1.1 | 6 / 4 | |
| 1000.1.0 | 6 / 4 | |
| 1000.0.5 | 6 / 4 | |
| 1000.0.4 | 6 / 4 | |
| 1000.0.3 | 6 / 4 | |
| 1000.0.2 | 6 / 4 | |
| 1000.0.1 | 6 / 4 | |
| 1000.0.0 | 6 / 4 |
v1000.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1000.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1000.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1000.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1000.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1000.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1000.1.0
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.