@pnpm/package-bins
Returns bins of a package
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
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 1000.0.18 | 3 / 3 | |
| 1000.0.17 | 3 / 3 | |
| 1000.0.16 | 3 / 2 | |
| 1000.0.15 | 3 / 2 | |
| 1000.0.14 | 3 / 2 | |
| 1000.0.13 | 3 / 2 | |
| 1000.0.12 | 3 / 2 | |
| 1000.0.11 | 3 / 2 | |
| 1000.0.10 | 3 / 2 | |
| 1000.0.9 | 3 / 2 | |
| 1000.0.8 | 3 / 2 | |
| 1000.0.7 | 3 / 2 | |
| 1000.0.6 | 3 / 2 | |
| 1000.0.5 | 3 / 2 | |
| 1000.0.4 | 3 / 2 | |
| 1000.0.3 | 3 / 2 | |
| 1000.0.2 | 3 / 2 | |
| 1000.0.1 | 3 / 2 | |
| 1000.0.0 | 3 / 2 |
v1000.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1000.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1000.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1000.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1000.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1000.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1000.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1000.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.