@izara_project/izara-core-library-resource-use
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 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 1.0.10 | 0 / 1 | |
| 1.0.9 | 7 / 1 | |
| 1.0.8 | 7 / 1 | |
| 1.0.7 | 7 / 1 | |
| 1.0.6 | 6 / 1 | |
| 1.0.5 | 6 / 1 | |
| 1.0.4 | 6 / 1 | |
| 1.0.3 | 6 / 1 |
v1.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.