@ckbox/components
UI components of CKBox
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): Known implicit dependency; stable pattern for this package type. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): Config-referenced dependency; stable for React component library. | ai | |
| phantom-deps | phantom-dep:blurhash | AI (phantom-deps): Config-referenced dependency; stable for this package. | ai | |
| phantom-deps | phantom-dep:dnd-core | AI (phantom-deps): Config-referenced dependency; stable for this package. | ai | |
| phantom-deps | phantom-dep:react-focus-lock | AI (phantom-deps): Config-referenced dependency; stable for this package. | ai | |
| phantom-deps | phantom-dep:react-remove-scroll | AI (phantom-deps): Config-referenced dependency; stable for this package. | ai | |
| phantom-deps | phantom-dep:react-dnd-html5-backend | AI (phantom-deps): Config-referenced dependency; stable for this package. | ai | |
| phantom-deps | phantom-dep:@types/react-transition-group | AI (phantom-deps): Framework-scoped package loaded by convention; stable for this package. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 2.11.0 | 12 / 0 | |
| 2.10.1 | 12 / 0 | |
| 2.10.0 | 12 / 0 | |
| 2.9.2 | 12 / 0 | |
| 2.9.1 | 12 / 0 | |
| 2.9.0 | 12 / 0 | |
| 2.8.2 | 12 / 0 | |
| 2.8.1 | 12 / 0 | |
| 2.8.0 | 12 / 0 |
v2.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.