@ckeditor/ckeditor5-ui
The UI framework and standard UI library of 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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@ckeditor/ckeditor5-core | AI (dependencies): Sibling CKEditor5 monorepo package published at the same version; expected dependency pattern for this package. | ai | |
| dependencies | unvetted-dep:@ckeditor/ckeditor5-icons | AI (dependencies): Sibling CKEditor5 monorepo package published at the same version; expected dependency pattern for this package. | ai | |
| dependencies | unvetted-dep:@ckeditor/ckeditor5-utils | AI (dependencies): Sibling CKEditor5 monorepo package published at the same version; expected dependency pattern for this package. | ai | |
| dependencies | unvetted-dep:@ckeditor/ckeditor5-engine | AI (dependencies): Sibling CKEditor5 monorepo package published at the same version; expected dependency pattern for this package. | ai | |
| dependencies | unvetted-dep:@ckeditor/ckeditor5-editor-multi-root | AI (dependencies): Sibling CKEditor5 monorepo package published at the same version; expected dependency pattern for this package. | ai | |
| dependencies | unvetted-dep:color-parse | AI (dependencies): Small, focused color parsing utility with no known security issues; stable dependency for a UI library with color picker functionality. | ai | |
| dependencies | unvetted-dep:vanilla-colorful | AI (dependencies): Lightweight color picker web component library; appropriate dependency for a UI framework package with color picker support. | ai | |
| phantom-deps | phantom-dep:@types/color-convert | AI (phantom-deps): @types packages are type declarations used at compile time; not being directly imported at runtime is expected behavior. | ai | |
| phantom-deps | phantom-dep:@ckeditor/ckeditor5-editor-multi-root | AI (phantom-deps): Same-org sibling package; may be used indirectly via type references or re-exports in the monorepo build. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 48.2.0 | 10 / 0 | |
| 48.1.1 | 10 / 0 | |
| 48.1.0 | 10 / 0 | |
| 48.0.1 | 10 / 0 | |
| 48.0.0 | 10 / 0 | |
| 47.7.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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v48.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v48.1.0
1 findingPackage 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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v47.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v47.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v47.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v47.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v47.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v47.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v47.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.