@computesdk/k8s
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:koa | AI (typosquat): Scoped @computesdk/k8s package; Levenshtein match to 'koa' is coincidental, not a typosquat. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped @computesdk/k8s package; Levenshtein match to 'qs' is coincidental, not a typosquat. | ai | |
| phantom-deps | phantom-dep:computesdk | AI (phantom-deps): computesdk is a declared runtime dependency; phantom-dep heuristic misfires on this package structure. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.2.2 | 3 / 8 | |
| 0.2.1 | 3 / 8 | |
| 0.2.0 | 3 / 8 | |
| 0.1.1 | 3 / 8 | |
| 0.1.0 | 3 / 8 |
v0.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.