@ckeditor/ckeditor5-case-change
Case change 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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@ckeditor/ckeditor5-ui | AI (dependencies): First-party CKEditor 5 dependency from the same org scope; expected internal dependency for all CKEditor 5 plugins. | ai | |
| dependencies | unvetted-dep:@ckeditor/ckeditor5-core | AI (dependencies): First-party CKEditor 5 dependency from the same org scope; expected internal dependency for all CKEditor 5 plugins. | ai | |
| dependencies | unvetted-dep:@ckeditor/ckeditor5-utils | AI (dependencies): First-party CKEditor 5 dependency from the same org scope; expected internal dependency for all CKEditor 5 plugins. | ai | |
| dependencies | unvetted-dep:@ckeditor/ckeditor5-engine | AI (dependencies): First-party CKEditor 5 dependency from the same org scope; expected internal dependency for all CKEditor 5 plugins. | ai | |
| phantom-deps | phantom-dep:@ckeditor/ckeditor5-ui | AI (phantom-deps): CKEditor 5 packages compile to dist/; imports may not be directly traceable. Same-org phantom deps are a known false positive for this ecosystem. | ai | |
| phantom-deps | phantom-dep:@ckeditor/ckeditor5-icons | AI (phantom-deps): CKEditor 5 packages compile to dist/; imports may not be directly traceable. Same-org phantom deps are a known false positive for this ecosystem. | ai | |
| phantom-deps | phantom-dep:@ckeditor/ckeditor5-engine | AI (phantom-deps): CKEditor 5 packages compile to dist/; imports may not be directly traceable. Same-org phantom deps are a known false positive for this ecosystem. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 48.2.0 | 5 / 0 | |
| 48.1.1 | 5 / 0 | |
| 48.1.0 | 5 / 0 | |
| 48.0.1 | 5 / 0 | |
| 48.0.0 | 5 / 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.