@ckeditor/ckeditor5-link
Link 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 | large-new-source-files | AI (source-diff): CKEditor ships build/ directory with bundled output; large file count is normal for this package's structure. | ai | |
| source-diff | obfuscated-file:build/link.js | AI (source-diff): Standard minified webpack/rollup build output for CKEditor plugin; contains CSS and translations bundle, not obfuscation. | ai | |
| phantom-deps | phantom-dep:@ckeditor/ckeditor5-image | AI (phantom-deps): Same-org optional/peer dependency pattern; CKEditor plugins cross-reference within the monorepo. | ai | |
| dependencies | unvetted-dep:@ckeditor/ckeditor5-icons | AI (dependencies): Sibling @ckeditor/* monorepo package pinned to same version; legitimate dependency for this package family. | ai | |
| dependencies | unvetted-dep:@ckeditor/ckeditor5-image | AI (dependencies): Sibling @ckeditor/* monorepo package pinned to same version; legitimate dependency for this package family. | ai | |
| dependencies | unvetted-dep:@ckeditor/ckeditor5-utils | AI (dependencies): Sibling @ckeditor/* monorepo package pinned to same version; legitimate dependency for this package family. | ai | |
| dependencies | unvetted-dep:@ckeditor/ckeditor5-engine | AI (dependencies): Sibling @ckeditor/* monorepo package pinned to same version; legitimate dependency for this package family. | ai | |
| dependencies | unvetted-dep:@ckeditor/ckeditor5-ui | AI (dependencies): Sibling @ckeditor/* monorepo package pinned to same version; legitimate dependency for this package family. | ai | |
| dependencies | unvetted-dep:@ckeditor/ckeditor5-widget | AI (dependencies): Sibling @ckeditor/* monorepo package pinned to same version; legitimate dependency for this package family. | ai | |
| dependencies | unvetted-dep:@ckeditor/ckeditor5-clipboard | AI (dependencies): Sibling @ckeditor/* monorepo package pinned to same version; legitimate dependency for this package family. | ai | |
| phantom-deps | phantom-dep:@ckeditor/ckeditor5-enter | AI (phantom-deps): Same org scope; phantom dep in monorepo packages is a common packaging artifact, not a security concern. | ai | |
| provenance | no-provenance | AI (provenance): CKEditor 5 is a well-established project; lack of Sigstore provenance is common and not a disqualifier here. | ai | |
| dependencies | unvetted-dep:@ckeditor/ckeditor5-typing | AI (dependencies): Sibling @ckeditor/* monorepo package pinned to same version; legitimate dependency for this package family. | ai | |
| dependencies | unvetted-dep:@ckeditor/ckeditor5-core | AI (dependencies): Sibling @ckeditor/* monorepo package pinned to same version; legitimate dependency for this package family. | ai | |
| dependencies | unvetted-dep:@ckeditor/ckeditor5-enter | AI (dependencies): Sibling @ckeditor/* monorepo package pinned to same version; legitimate dependency for this package family. | 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
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
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.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.