@ckeditor/ckeditor5-media-embed
Media embed 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/media-embed.js | AI (source-diff): CKEditor 5 plugins routinely ship webpack-bundled DLL build artifacts in build/. The sample shows standard CKEditor translation data and CSS — not obfuscation for malicious purposes. | ai | |
| source-diff | large-new-source-files | AI (source-diff): CKEditor 5 packages regularly add large numbers of source files across version branches; this is consistent with the package's established release pattern. | ai | |
| dependencies | unvetted-dep:@ckeditor/ckeditor5-undo | AI (dependencies): First-party sibling package from the CKEditor 5 monorepo, released in lockstep. Not an independent risk. | ai | |
| dependencies | unvetted-dep:@ckeditor/ckeditor5-icons | AI (dependencies): First-party sibling package from the CKEditor 5 monorepo, released in lockstep. Not an independent risk. | ai | |
| dependencies | unvetted-dep:@ckeditor/ckeditor5-utils | AI (dependencies): First-party sibling package from the CKEditor 5 monorepo, released in lockstep. Not an independent risk. | ai | |
| dependencies | unvetted-dep:@ckeditor/ckeditor5-engine | AI (dependencies): First-party sibling package from the CKEditor 5 monorepo, released in lockstep. Not an independent risk. | ai | |
| dependencies | unvetted-dep:@ckeditor/ckeditor5-ui | AI (dependencies): First-party sibling package from the CKEditor 5 monorepo, released in lockstep. Not an independent risk. | ai | |
| dependencies | unvetted-dep:@ckeditor/ckeditor5-widget | AI (dependencies): First-party sibling package from the CKEditor 5 monorepo, released in lockstep. Not an independent risk. | ai | |
| dependencies | unvetted-dep:@ckeditor/ckeditor5-clipboard | AI (dependencies): First-party sibling package from the CKEditor 5 monorepo, released in lockstep. Not an independent risk. | ai | |
| provenance | no-provenance | AI (provenance): Established 7+ year old package from CKSource. Lack of Sigstore provenance is not a meaningful risk signal for this publisher. | ai | |
| dependencies | unvetted-dep:@ckeditor/ckeditor5-typing | AI (dependencies): First-party sibling package from the CKEditor 5 monorepo, released in lockstep. Not an independent risk. | ai | |
| dependencies | unvetted-dep:@ckeditor/ckeditor5-core | AI (dependencies): First-party sibling package from the CKEditor 5 monorepo, released in lockstep. Not an independent risk. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 48.2.0 | 9 / 0 | |
| 48.1.1 | 9 / 0 | |
| 48.1.0 | 9 / 0 | |
| 48.0.1 | 9 / 0 | |
| 48.0.0 | 9 / 0 | |
| 47.7.2 | 10 / 0 | |
| 47.7.1 | 10 / 0 | |
| 47.7.0 | 10 / 0 | |
| 47.6.2 | 10 / 0 | |
| 47.6.1 | 10 / 0 | |
| 47.6.0 | 10 / 0 | |
| 47.5.0 | 10 / 0 | |
| 47.4.0 | 10 / 0 | |
| 47.3.0 | 10 / 0 | |
| 47.2.0 | 10 / 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
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. Consider requesting the maintainer enable provenance via CI/CD.
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.