tsafe
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 |
|---|---|---|
| 1.8.12 | 0 / 0 | |
| 1.8.11 | 0 / 0 | |
| 1.8.10 | 0 / 0 | |
| 1.8.9 | 0 / 0 | |
| 1.8.8 | 0 / 0 | |
| 1.8.7 | 0 / 0 | |
| 1.8.6 | 0 / 0 | |
| 1.8.5 | 0 / 15 | |
| 1.8.4 | 0 / 15 | |
| 1.8.3 | 0 / 15 | |
| 1.8.2 | 0 / 15 | |
| 1.8.1 | 0 / 19 | |
| 1.8.0 | 0 / 19 | |
| 1.7.5 | 0 / 19 | |
| 1.7.4 | 0 / 14 | |
| 1.7.3 | 0 / 14 | |
| 1.7.2 | 0 / 13 | |
| 1.7.1 | 0 / 13 | |
| 1.7.0 | 0 / 13 |
v1.8.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.