@pnpm/fs.find-packages
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): pnpm monorepo packages published by zkochan consistently lack Sigstore provenance; this is a stable pattern for this publisher and not a security concern. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 1000.0.25 | 5 / 1 | |
| 1000.0.23 | 5 / 1 | |
| 1000.0.22 | 5 / 1 | |
| 1000.0.21 | 5 / 1 | |
| 1000.0.20 | 5 / 1 | |
| 1000.0.19 | 5 / 1 | |
| 1000.0.18 | 5 / 1 | |
| 1000.0.17 | 5 / 1 | |
| 1000.0.16 | 5 / 1 | |
| 1000.0.15 | 5 / 1 | |
| 1000.0.14 | 5 / 1 | |
| 1000.0.13 | 5 / 1 | |
| 1000.0.12 | 5 / 1 | |
| 1000.0.11 | 5 / 1 | |
| 1000.0.10 | 5 / 1 | |
| 1000.0.9 | 5 / 1 | |
| 1000.0.8 | 5 / 1 | |
| 1000.0.7 | 5 / 1 | |
| 1000.0.6 | 5 / 1 | |
| 1000.0.5 | 5 / 1 | |
| 1000.0.4 | 5 / 1 | |
| 1000.0.3 | 5 / 1 | |
| 1000.0.2 | 5 / 1 | |
| 1000.0.1 | 5 / 1 | |
| 1000.0.0 | 5 / 1 |
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.