@skyscanner/bpk-svgs
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
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 20.14.0 | 0 / 22 | |
| 20.13.0 | 0 / 22 | |
| 20.12.0 | 0 / 22 | |
| 20.11.0 | 0 / 22 | |
| 20.10.0 | 0 / 22 | |
| 20.9.3 | 0 / 22 | |
| 20.9.2 | 0 / 22 | |
| 20.9.1 | 0 / 22 | |
| 20.9.0 | 0 / 22 | |
| 20.8.0 | 0 / 22 | |
| 20.7.0 | 0 / 22 | |
| 20.6.0 | 0 / 22 | |
| 20.5.0 | 0 / 22 | |
| 20.4.1 | 0 / 21 | |
| 20.4.0 | 0 / 21 | |
| 20.3.0 | 0 / 21 | |
| 20.1.1 | 0 / 21 | |
| 20.1.0 | 0 / 21 | |
| 20.0.0 | 0 / 21 |
v20.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.