@cargo-ai/utils
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Internal scoped package; missing repo/keywords/homepage is expected for private org utilities published under @cargo-ai/. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 1.0.23 | 9 / 11 | |
| 1.0.22 | 9 / 11 | |
| 1.0.21 | 9 / 11 | |
| 1.0.20 | 11 / 12 | |
| 1.0.19 | 11 / 12 | |
| 1.0.18 | 11 / 12 | |
| 1.0.17 | 9 / 12 | |
| 1.0.16 | 9 / 12 | |
| 1.0.15 | 9 / 12 | |
| 1.0.14 | 9 / 12 | |
| 1.0.13 | 9 / 12 | |
| 1.0.12 | 9 / 12 | |
| 1.0.11 | 9 / 12 | |
| 1.0.10 | 9 / 12 | |
| 1.0.9 | 9 / 12 | |
| 1.0.8 | 9 / 12 | |
| 1.0.7 | 9 / 12 | |
| 1.0.6 | 9 / 12 | |
| 1.0.5 | 9 / 12 | |
| 1.0.4 | 9 / 12 |
v1.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.