@oscarpalmer/toretto
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 60 of 60)
| Version | Deps | Published |
|---|---|---|
| 0.48.0 | 1 / 9 | |
| 0.47.3 | 1 / 9 | |
| 0.47.2 | 1 / 9 | |
| 0.47.1 | 1 / 9 | |
| 0.47.0 | 1 / 9 | |
| 0.46.0 | 1 / 9 | |
| 0.45.0 | 1 / 9 | |
| 0.44.0 | 1 / 9 | |
| 0.43.0 | 1 / 9 | |
| 0.42.0 | 1 / 8 | |
| 0.41.0 | 1 / 8 | |
| 0.40.0 | 1 / 8 | |
| 0.39.2 | 1 / 11 | |
| 0.39.1 | 1 / 11 | |
| 0.39.0 | 1 / 10 | |
| 0.38.0 | 1 / 10 | |
| 0.37.2 | 1 / 10 | |
| 0.37.1 | 1 / 10 | |
| 0.37.0 | 1 / 10 | |
| 0.36.0 | 1 / 10 | |
| 0.35.0 | 1 / 10 | |
| 0.34.0 | 1 / 10 | |
| 0.33.0 | 1 / 10 | |
| 0.32.0 | 1 / 10 | |
| 0.31.0 | 1 / 10 | |
| 0.30.1 | 1 / 10 | |
| 0.30.0 | 1 / 10 | |
| 0.29.0 | 1 / 12 | |
| 0.28.0 | 1 / 12 | |
| 0.27.0 | 1 / 11 | |
| 0.26.1 | 1 / 12 | |
| 0.26.0 | 1 / 12 | |
| 0.25.0 | 1 / 12 | |
| 0.24.0 | 1 / 11 | |
| 0.23.1 | 1 / 11 | |
| 0.23.0 | 1 / 11 | |
| 0.22.0 | 1 / 13 | |
| 0.21.0 | 1 / 13 | |
| 0.20.0 | 1 / 9 | |
| 0.19.0 | 1 / 9 | |
| 0.18.0 | 1 / 9 | |
| 0.17.0 | 1 / 9 | |
| 0.16.0 | 1 / 9 | |
| 0.15.1 | 1 / 9 | |
| 0.15.0 | 1 / 9 | |
| 0.14.0 | 1 / 7 | |
| 0.13.0 | 1 / 7 | |
| 0.12.1 | 1 / 6 | |
| 0.12.0 | 1 / 6 | |
| 0.11.0 | 1 / 6 | |
| 0.10.0 | 1 / 6 | |
| 0.9.0 | 1 / 6 | |
| 0.8.0 | 1 / 6 | |
| 0.7.0 | 1 / 6 | |
| 0.6.0 | 1 / 6 | |
| 0.5.0 | 1 / 6 | |
| 0.4.0 | 1 / 6 | |
| 0.3.0 | 1 / 6 | |
| 0.2.0 | 1 / 6 | |
| 0.1.0 | 0 / 6 |
v0.48.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.47.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.47.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.47.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.47.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.