@vtx/utils
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 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 1.0.29 | 6 / 27 | |
| 1.0.28 | 6 / 27 | |
| 1.0.27 | 6 / 27 | |
| 1.0.26 | 6 / 27 | |
| 1.0.25 | 6 / 26 | |
| 1.0.24 | 6 / 27 | |
| 1.0.23 | 6 / 27 | |
| 1.0.22 | 6 / 26 | |
| 1.0.21 | 6 / 26 | |
| 1.0.20 | 6 / 26 | |
| 1.0.19 | 6 / 26 | |
| 1.0.18 | 6 / 26 | |
| 1.0.17 | 5 / 26 | |
| 1.0.16 | 5 / 26 | |
| 1.0.15 | 5 / 26 | |
| 1.0.14 | 5 / 26 | |
| 1.0.13 | 5 / 26 | |
| 1.0.12 | 3 / 26 | |
| 1.0.11 | 3 / 26 | |
| 1.0.10 | 3 / 26 | |
| 1.0.9 | 3 / 26 | |
| 1.0.8 | 3 / 26 |
v1.0.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.