@ckeditor/ckeditor5-list
Ordered and unordered lists feature to 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): Sibling @ckeditor/* monorepo package released simultaneously; unvetted status is a pipeline artifact, not a genuine risk. | ai | |
| dependencies | unvetted-dep:@ckeditor/ckeditor5-core | AI (dependencies): Sibling @ckeditor/* monorepo package released simultaneously; unvetted status is a pipeline artifact, not a genuine risk. | ai | |
| dependencies | unvetted-dep:@ckeditor/ckeditor5-font | AI (dependencies): Sibling @ckeditor/* monorepo package released simultaneously; unvetted status is a pipeline artifact, not a genuine risk. | ai | |
| dependencies | unvetted-dep:@ckeditor/ckeditor5-enter | AI (dependencies): Sibling @ckeditor/* monorepo package released simultaneously; unvetted status is a pipeline artifact, not a genuine risk. | ai | |
| dependencies | unvetted-dep:@ckeditor/ckeditor5-icons | AI (dependencies): Sibling @ckeditor/* monorepo package released simultaneously; unvetted status is a pipeline artifact, not a genuine risk. | ai | |
| dependencies | unvetted-dep:@ckeditor/ckeditor5-utils | AI (dependencies): Sibling @ckeditor/* monorepo package released simultaneously; unvetted status is a pipeline artifact, not a genuine risk. | ai | |
| dependencies | unvetted-dep:@ckeditor/ckeditor5-engine | AI (dependencies): Sibling @ckeditor/* monorepo package released simultaneously; unvetted status is a pipeline artifact, not a genuine risk. | ai | |
| dependencies | unvetted-dep:@ckeditor/ckeditor5-typing | AI (dependencies): Sibling @ckeditor/* monorepo package released simultaneously; unvetted status is a pipeline artifact, not a genuine risk. | ai | |
| dependencies | unvetted-dep:@ckeditor/ckeditor5-clipboard | AI (dependencies): Sibling @ckeditor/* monorepo package released simultaneously; unvetted status is a pipeline artifact, not a genuine risk. | ai | |
| provenance | no-provenance | AI (provenance): CKEditor 5 packages do not use Sigstore provenance; this is consistent across all versions of this well-established publisher. | ai | |
| license | uncommon-license:SEE LICENSE IN LICENSE.md | AI (license): Standard CKEditor 5 license expression used consistently across all @ckeditor/* packages; not a risk signal. | ai |
Versions (showing 15 of 15)
| 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 | 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 | 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
1 finding[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. Consider requesting the maintainer enable provenance via CI/CD.
v47.6.2
1 finding[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. 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.