@pnpm/real-hoist
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 canonical pnpm maintainer; publisher change from pnpmuser back to zkochan is expected for this org package. | ai |
Versions (showing 34 of 34)
| Version | Deps | Published |
|---|---|---|
| 1001.0.33 | 4 / 4 | |
| 1001.0.32 | 4 / 4 | |
| 1001.0.31 | 4 / 4 | |
| 1001.0.30 | 4 / 4 | |
| 1001.0.29 | 4 / 4 | |
| 1001.0.28 | 4 / 4 | |
| 1001.0.27 | 4 / 4 | |
| 1001.0.26 | 4 / 4 | |
| 1001.0.25 | 4 / 4 | |
| 1001.0.24 | 4 / 4 | |
| 1001.0.23 | 4 / 4 | |
| 1001.0.22 | 4 / 4 | |
| 1001.0.21 | 4 / 4 | |
| 1001.0.20 | 4 / 4 | |
| 1001.0.19 | 4 / 4 | |
| 1001.0.18 | 4 / 4 | |
| 1001.0.17 | 4 / 4 | |
| 1001.0.16 | 4 / 4 | |
| 1001.0.15 | 4 / 4 | |
| 1001.0.14 | 4 / 4 | |
| 1001.0.13 | 4 / 4 | |
| 1001.0.12 | 4 / 4 | |
| 1001.0.11 | 4 / 4 | |
| 1001.0.10 | 4 / 4 | |
| 1001.0.9 | 4 / 4 | |
| 1001.0.8 | 4 / 4 | |
| 1001.0.7 | 4 / 4 | |
| 1001.0.6 | 4 / 4 | |
| 1001.0.5 | 4 / 4 | |
| 1001.0.4 | 4 / 4 | |
| 1001.0.3 | 4 / 4 | |
| 1001.0.2 | 4 / 4 | |
| 1001.0.1 | 4 / 4 | |
| 1001.0.0 | 4 / 4 |
v1001.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1001.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.