@ckbox/core
Core functionality 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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@ckbox/i18n | AI (dependencies): Same org scope (@ckbox); sibling package from CKSource, stable pattern across versions. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Established CKEditor org package with 101 versions; resumed publishing is consistent with product lifecycle, not takeover. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): Referenced in config files; stable false positive for this bundled package. | ai | |
| phantom-deps | phantom-dep:nanoid | AI (phantom-deps): Referenced in config files; stable false positive for this bundled package. | ai | |
| phantom-deps | phantom-dep:crypto-js | AI (phantom-deps): Referenced in config files; stable false positive for this bundled package. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): @ckbox/core is the legitimate CKBox core module by CKSource; not a typosquat of cors. | ai | |
| phantom-deps | phantom-dep:react-hook-form | AI (phantom-deps): Referenced in config files; stable false positive for this bundled package. | ai | |
| phantom-deps | phantom-dep:@tanstack/react-query | AI (phantom-deps): Referenced in config files; stable false positive for this bundled package. | ai | |
| phantom-deps | phantom-dep:@ckbox/i18n | AI (phantom-deps): Same-org sibling package; phantom-dep heuristic unreliable for monorepo bundles. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a known implicit runtime dependency for TypeScript-compiled packages. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 2.13.0 | 8 / 0 | |
| 2.12.0 | 8 / 0 | |
| 2.11.1 | 8 / 0 | |
| 2.11.0 | 8 / 0 | |
| 2.10.1 | 8 / 0 | |
| 2.10.0 | 8 / 0 | |
| 2.9.2 | 8 / 0 | |
| 2.9.1 | 8 / 0 | |
| 2.9.0 | 8 / 0 | |
| 2.8.2 | 8 / 0 | |
| 2.8.1 | 8 / 0 | |
| 2.8.0 | 8 / 0 | |
| 2.6.1 | 8 / 0 | |
| 2.6.0 | 8 / 0 | |
| 2.5.2 | 8 / 0 | |
| 2.5.1 | 8 / 0 | |
| 2.5.0 | 8 / 0 | |
| 2.4.0 | 8 / 0 | |
| 2.3.1 | 8 / 0 | |
| 2.3.0 | 8 / 0 | |
| 2.2.0 | 8 / 0 | |
| 2.1.2 | 8 / 0 | |
| 2.1.1 | 8 / 0 | |
| 2.1.0 | 8 / 0 | |
| 2.0.0 | 8 / 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. Consider requesting the maintainer enable provenance via CI/CD.
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.