@ckeditor/ckeditor5-ckbox
CKBox integration for CKEditor 5.
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Version numbering gap in CKEditor monorepo; publisher is long-standing trusted account. | ai | |
| source-diff | obfuscated-file:build/ckbox.js | AI (source-diff): Standard webpack bundle for CKEditor plugin; not obfuscation. | ai | |
| phantom-deps | phantom-dep:@ckeditor/ckeditor5-image | AI (phantom-deps): Same-org CKEditor dep; peer/transitive usage pattern stable for this package. | ai | |
| dependencies | unvetted-dep:@ckeditor/ckeditor5-link | AI (dependencies): Legitimate sibling CKEditor 5 package from the same monorepo and release. Expected dependency. | ai | |
| dependencies | unvetted-dep:@ckeditor/ckeditor5-image | AI (dependencies): Legitimate sibling CKEditor 5 package from the same monorepo and release. Expected dependency. | ai | |
| dependencies | unvetted-dep:@ckeditor/ckeditor5-utils | AI (dependencies): Legitimate sibling CKEditor 5 package from the same monorepo and release. Expected dependency. | ai | |
| dependencies | unvetted-dep:blurhash | AI (dependencies): blurhash is a well-known, benign image placeholder library with no security concerns. Stable dependency for this package. | ai | |
| dependencies | unvetted-dep:@ckeditor/ckeditor5-upload | AI (dependencies): Legitimate sibling CKEditor 5 package from the same monorepo and release. Expected dependency. | ai | |
| dependencies | unvetted-dep:@ckeditor/ckeditor5-cloud-services | AI (dependencies): Legitimate sibling CKEditor 5 package from the same monorepo and release. Expected dependency. | ai | |
| provenance | no-provenance | AI (provenance): CKEditor 5 is a large, established project. Lack of Sigstore provenance is common and not a risk signal for this well-known publisher. | ai | |
| dependencies | unvetted-dep:@ckeditor/ckeditor5-engine | AI (dependencies): Legitimate sibling CKEditor 5 package from the same monorepo and release. Expected dependency. | ai | |
| dependencies | unvetted-dep:@ckeditor/ckeditor5-ui | AI (dependencies): Legitimate sibling CKEditor 5 package from the same monorepo and release. Expected dependency. | ai | |
| dependencies | unvetted-dep:@ckeditor/ckeditor5-core | AI (dependencies): Legitimate sibling CKEditor 5 package from the same monorepo and release. Expected dependency. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 48.2.0 | 11 / 0 | |
| 48.1.1 | 11 / 0 | |
| 48.1.0 | 11 / 0 | |
| 48.0.1 | 11 / 0 | |
| 48.0.0 | 11 / 0 | |
| 47.7.2 | 11 / 0 | |
| 47.7.1 | 11 / 0 | |
| 47.7.0 | 11 / 0 | |
| 47.6.2 | 11 / 0 | |
| 47.6.1 | 11 / 0 | |
| 47.6.0 | 11 / 0 | |
| 47.5.0 | 11 / 0 | |
| 47.4.0 | 11 / 0 | |
| 47.3.0 | 11 / 0 | |
| 47.2.0 | 11 / 0 |
v48.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v48.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v48.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v48.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v48.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v47.7.2
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v47.7.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v47.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v47.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v47.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v47.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v47.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v47.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v47.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v47.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.