@goldstack/utils-git
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 |
|---|---|---|
| 0.2.27 | 2 / 8 | |
| 0.2.26 | 2 / 8 | |
| 0.2.25 | 2 / 8 | |
| 0.2.24 | 2 / 8 | |
| 0.2.23 | 2 / 8 | |
| 0.2.22 | 2 / 8 | |
| 0.2.21 | 2 / 8 | |
| 0.2.20 | 2 / 8 | |
| 0.2.19 | 2 / 8 | |
| 0.2.18 | 2 / 8 | |
| 0.2.17 | 2 / 8 | |
| 0.2.16 | 2 / 8 | |
| 0.2.15 | 2 / 8 | |
| 0.2.14 | 2 / 8 | |
| 0.2.13 | 2 / 8 | |
| 0.2.12 | 2 / 8 | |
| 0.2.11 | 2 / 8 | |
| 0.2.10 | 2 / 8 |
v0.2.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.