@cargo-ai/api
Cargo API client and types
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@cargo-ai/types | AI (phantom-deps): Same-org sibling dep; likely used transitively or in type declarations. | ai | |
| phantom-deps | phantom-dep:@cargo-ai/utils | AI (phantom-deps): Same-org sibling dep; likely used transitively or in type declarations. | ai | |
| typosquat | typosquat.levenshtein:hapi | AI (typosquat): Scoped @cargo-ai/* monorepo package; not a typosquat of hapi. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped @cargo-ai/* monorepo package; not a typosquat of pg. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped @cargo-ai/* monorepo package; not a typosquat of joi. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): Scoped @cargo-ai/* monorepo package; not a typosquat of ajv. | ai |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 1.0.26 | 4 / 7 | |
| 1.0.25 | 4 / 7 | |
| 1.0.24 | 4 / 7 | |
| 1.0.23 | 4 / 7 | |
| 1.0.22 | 4 / 7 | |
| 1.0.21 | 4 / 7 | |
| 1.0.20 | 4 / 7 | |
| 1.0.19 | 4 / 7 | |
| 1.0.18 | 4 / 7 | |
| 1.0.17 | 4 / 7 | |
| 1.0.16 | 4 / 7 | |
| 1.0.15 | 4 / 7 | |
| 1.0.14 | 4 / 7 | |
| 1.0.13 | 4 / 7 | |
| 1.0.12 | 4 / 7 | |
| 1.0.11 | 4 / 7 | |
| 1.0.10 | 4 / 7 | |
| 1.0.9 | 4 / 7 | |
| 1.0.8 | 4 / 7 | |
| 1.0.7 | 4 / 7 | |
| 1.0.6 | 4 / 7 | |
| 1.0.5 | 4 / 7 | |
| 1.0.4 | 4 / 7 | |
| 1.0.3 | 4 / 7 | |
| 1.0.2 | 4 / 7 | |
| 1.0.1 | 4 / 7 |
v1.0.26
2 findingsPackage name '@cargo-ai/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.25
2 findingsPackage name '@cargo-ai/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.24
2 findingsPackage name '@cargo-ai/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.22
2 findingsPackage name '@cargo-ai/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.21
2 findingsPackage name '@cargo-ai/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.20
2 findingsPackage name '@cargo-ai/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.19
2 findingsPackage name '@cargo-ai/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.18
2 findingsPackage name '@cargo-ai/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.17
2 findingsPackage name '@cargo-ai/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.16
2 findingsPackage name '@cargo-ai/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.15
2 findingsPackage name '@cargo-ai/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.14
2 findingsPackage name '@cargo-ai/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.13
2 findingsPackage name '@cargo-ai/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.12
2 findingsPackage name '@cargo-ai/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.11
2 findingsPackage name '@cargo-ai/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.10
2 findingsPackage name '@cargo-ai/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.9
2 findingsPackage name '@cargo-ai/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.8
2 findingsPackage name '@cargo-ai/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.7
2 findingsPackage name '@cargo-ai/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.6
2 findingsPackage name '@cargo-ai/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.5
2 findingsPackage name '@cargo-ai/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.4
2 findingsPackage name '@cargo-ai/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
2 findingsPackage name '@cargo-ai/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
2 findingsPackage name '@cargo-ai/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
2 findingsPackage name '@cargo-ai/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.