@camox/api
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:hapi | AI (typosquat): Scoped package @camox/api; Levenshtein match on 'hapi' is a coincidental substring hit, not impersonation. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped package @camox/api; no relation to 'pg', false positive. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped package @camox/api; no relation to 'joi', false positive. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): Scoped package @camox/api; no relation to 'ajv', false positive. | ai | |
| phantom-deps | phantom-dep:@hono/zod-validator | AI (phantom-deps): @hono/zod-validator is declared in dependencies and used via config/re-export; phantom-dep heuristic misfires here. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 0.7.0 | 13 / 7 | |
| 0.6.1 | 13 / 7 | |
| 0.6.0 | 13 / 7 | |
| 0.5.2 | 13 / 7 | |
| 0.5.1 | 13 / 7 | |
| 0.5.0 | 13 / 7 | |
| 0.4.2 | 13 / 7 | |
| 0.4.1 | 13 / 7 | |
| 0.4.0 | 13 / 7 | |
| 0.3.1 | 13 / 7 |
v0.7.0
2 findingsPackage name '@camox/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.
v0.6.1
2 findingsPackage name '@camox/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.
v0.6.0
2 findingsPackage name '@camox/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.
v0.5.2
2 findingsPackage name '@camox/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.
v0.5.1
2 findingsPackage name '@camox/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.
v0.5.0
2 findingsPackage name '@camox/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.
v0.4.2
2 findingsPackage name '@camox/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.
v0.4.1
2 findingsPackage name '@camox/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.
v0.4.0
2 findingsPackage name '@camox/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.
v0.3.1
2 findingsPackage name '@camox/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.