@c-rex/constants
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 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 0.1.17 | 0 / 7 | |
| 0.1.16 | 0 / 7 | |
| 0.1.15 | 0 / 7 | |
| 0.1.14 | 0 / 7 | |
| 0.1.13 | 0 / 7 | |
| 0.1.12 | 0 / 7 | |
| 0.1.11 | 0 / 7 | |
| 0.1.10 | 0 / 7 | |
| 0.1.9 | 0 / 7 | |
| 0.1.8 | 0 / 7 | |
| 0.1.7 | 0 / 7 | |
| 0.1.6 | 0 / 7 | |
| 0.1.5 | 0 / 7 | |
| 0.1.4 | 0 / 7 | |
| 0.1.3 | 0 / 7 | |
| 0.1.2 | 0 / 7 | |
| 0.1.1 | 0 / 7 | |
| 0.1.0 | 0 / 7 | |
| 0.0.9 | 0 / 7 | |
| 0.0.8 | 0 / 7 | |
| 0.0.7 | 0 / 7 | |
| 0.0.6 | 0 / 7 | |
| 0.0.4 | 0 / 7 | |
| 0.0.3 | 0 / 7 | |
| 0.0.2 | 0 / 7 | |
| 0.0.1 | 0 / 7 |
v0.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.