@ckeditor/ckeditor5-image
Image feature 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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:build/image.js | AI (source-diff): build/image.js is CKEditor's standard minified build output containing translation dictionaries and bundled code; expected for this package. | ai | |
| source-diff | large-new-source-files | AI (source-diff): CKEditor5-image ships ~195 source files as its normal package content; this is the package's standard size. | ai | |
| license | uncommon-license:SEE LICENSE IN LICENSE.md | AI (license): CKEditor uses 'SEE LICENSE IN LICENSE.md' for its dual GPL/commercial license; standard for all @ckeditor packages. | ai | |
| dependencies | unvetted-dep:@ckeditor/ckeditor5-icons | AI (dependencies): First-party CKEditor 5 monorepo sibling package, released in lockstep. Not a third-party risk. | ai | |
| dependencies | unvetted-dep:@ckeditor/ckeditor5-utils | AI (dependencies): First-party CKEditor 5 monorepo sibling package, released in lockstep. Not a third-party risk. | ai | |
| dependencies | unvetted-dep:@ckeditor/ckeditor5-engine | AI (dependencies): First-party CKEditor 5 monorepo sibling package, released in lockstep. Not a third-party risk. | ai | |
| dependencies | unvetted-dep:@ckeditor/ckeditor5-typing | AI (dependencies): First-party CKEditor 5 monorepo sibling package, released in lockstep. Not a third-party risk. | ai | |
| dependencies | unvetted-dep:@ckeditor/ckeditor5-ui | AI (dependencies): First-party CKEditor 5 monorepo sibling package, released in lockstep. Not a third-party risk. | ai | |
| dependencies | unvetted-dep:@ckeditor/ckeditor5-widget | AI (dependencies): First-party CKEditor 5 monorepo sibling package, released in lockstep. Not a third-party risk. | ai | |
| dependencies | unvetted-dep:@ckeditor/ckeditor5-clipboard | AI (dependencies): First-party CKEditor 5 monorepo sibling package, released in lockstep. Not a third-party risk. | ai | |
| provenance | no-provenance | AI (provenance): CKEditor 5 is a mature, high-download commercial package; absence of Sigstore provenance is consistent with their historical publishing practice. | ai | |
| dependencies | unvetted-dep:@ckeditor/ckeditor5-upload | AI (dependencies): First-party CKEditor 5 monorepo sibling package, released in lockstep. Not a third-party risk. | ai | |
| dependencies | unvetted-dep:@ckeditor/ckeditor5-core | AI (dependencies): First-party CKEditor 5 monorepo sibling package, released in lockstep. Not a third-party risk. | ai | |
| dependencies | unvetted-dep:@ckeditor/ckeditor5-undo | AI (dependencies): First-party CKEditor 5 monorepo sibling package, released in lockstep. Not a third-party risk. | 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 | 12 / 0 | |
| 47.7.1 | 12 / 0 | |
| 47.7.0 | 12 / 0 | |
| 47.6.2 | 12 / 0 | |
| 47.6.1 | 12 / 0 | |
| 47.6.0 | 12 / 0 | |
| 47.5.0 | 12 / 0 | |
| 47.4.0 | 12 / 0 | |
| 47.3.0 | 12 / 0 | |
| 47.2.0 | 12 / 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
1 finding[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
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.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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.