@ckbox/sdk-node
CKBox SDK
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
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 2.11.1 | 5 / 0 | |
| 2.11.0 | 5 / 0 | |
| 2.10.1 | 5 / 0 | |
| 2.10.0 | 5 / 0 | |
| 2.9.2 | 5 / 0 | |
| 2.9.1 | 5 / 0 | |
| 2.9.0 | 5 / 0 |
v2.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.