@pnpm/pick-registry-for-package
Picks the right registry for the package from a registries config
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 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 1000.0.17 | 1 / 1 | |
| 1000.0.16 | 1 / 1 | |
| 1000.0.15 | 1 / 1 | |
| 1000.0.14 | 1 / 1 | |
| 1000.0.13 | 1 / 1 | |
| 1000.0.12 | 1 / 1 | |
| 1000.0.11 | 1 / 1 | |
| 1000.0.10 | 1 / 1 | |
| 1000.0.9 | 1 / 1 | |
| 1000.0.8 | 1 / 1 | |
| 1000.0.7 | 1 / 1 | |
| 1000.0.6 | 1 / 1 | |
| 1000.0.5 | 1 / 1 | |
| 1000.0.4 | 1 / 1 | |
| 1000.0.3 | 1 / 1 | |
| 1000.0.2 | 1 / 1 | |
| 1000.0.1 | 1 / 1 | |
| 1000.0.0 | 1 / 1 |
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.