@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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | net-exec-file:dist/pdf.worker.min.mjs | AI (source-diff): This is the standard Mozilla PDF.js worker bundle; dynamic exec and network I/O are inherent to PDF.js design, not malware. | 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:tslib | AI (phantom-deps): Known implicit dependency; stable pattern for this package type. | 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 | |
| phantom-deps | phantom-dep:react-focus-lock | AI (phantom-deps): Config-referenced dependency; stable for this package. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 2.13.0 | 13 / 0 | |
| 2.12.0 | 13 / 0 | |
| 2.11.1 | 12 / 0 | |
| 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 | |
| 2.6.1 | 12 / 0 | |
| 2.6.0 | 12 / 0 | |
| 2.5.2 | 12 / 0 | |
| 2.5.1 | 12 / 0 | |
| 2.5.0 | 12 / 0 | |
| 2.4.0 | 12 / 0 | |
| 2.3.1 | 11 / 0 | |
| 2.3.0 | 11 / 0 | |
| 2.2.0 | 11 / 0 | |
| 2.1.2 | 11 / 0 | |
| 2.1.1 | 11 / 0 | |
| 2.1.0 | 11 / 0 | |
| 2.0.0 | 11 / 0 |
v2.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.