@goldstack/utils-esbuild
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.5.28 | 0 / 7 | |
| 0.5.27 | 0 / 7 | |
| 0.5.26 | 0 / 7 | |
| 0.5.24 | 0 / 7 | |
| 0.5.23 | 0 / 8 | |
| 0.5.22 | 0 / 8 | |
| 0.5.21 | 0 / 8 | |
| 0.5.20 | 0 / 8 | |
| 0.5.19 | 0 / 8 | |
| 0.5.18 | 0 / 8 | |
| 0.5.17 | 0 / 8 | |
| 0.5.16 | 0 / 8 | |
| 0.5.15 | 0 / 8 | |
| 0.5.14 | 0 / 8 | |
| 0.5.13 | 0 / 8 | |
| 0.5.12 | 0 / 8 | |
| 0.5.11 | 0 / 8 | |
| 0.5.10 | 0 / 8 |
v0.5.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.