@izara_project/izara-core-library-core
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 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 1.0.32 | 5 / 1 | |
| 1.0.31 | 5 / 1 | |
| 1.0.30 | 5 / 1 | |
| 1.0.29 | 5 / 1 | |
| 1.0.28 | 5 / 1 | |
| 1.0.27 | 5 / 1 | |
| 1.0.26 | 5 / 1 | |
| 1.0.25 | 9 / 1 | |
| 1.0.24 | 9 / 1 | |
| 1.0.23 | 9 / 1 | |
| 1.0.22 | 9 / 1 | |
| 1.0.21 | 9 / 1 | |
| 1.0.20 | 6 / 1 | |
| 1.0.19 | 6 / 1 | |
| 1.0.18 | 6 / 1 | |
| 1.0.17 | 7 / 1 | |
| 1.0.16 | 7 / 1 | |
| 1.0.15 | 5 / 1 | |
| 1.0.14 | 5 / 1 |
v1.0.19
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.