@ckeditor/ckeditor5-clipboard
Clipboard integration 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): Sibling CKEditor 5 monorepo package released in lockstep; unvetted status reflects pipeline ordering, not a security concern. | ai | |
| dependencies | unvetted-dep:@ckeditor/ckeditor5-core | AI (dependencies): Sibling CKEditor 5 monorepo package released in lockstep; unvetted status reflects pipeline ordering, not a security concern. | ai | |
| dependencies | unvetted-dep:@ckeditor/ckeditor5-utils | AI (dependencies): Sibling CKEditor 5 monorepo package released in lockstep; unvetted status reflects pipeline ordering, not a security concern. | ai | |
| dependencies | unvetted-dep:@ckeditor/ckeditor5-engine | AI (dependencies): Sibling CKEditor 5 monorepo package released in lockstep; unvetted status reflects pipeline ordering, not a security concern. | ai | |
| dependencies | unvetted-dep:@ckeditor/ckeditor5-widget | AI (dependencies): Sibling CKEditor 5 monorepo package released in lockstep; unvetted status reflects pipeline ordering, not a security concern. | ai | |
| provenance | no-provenance | AI (provenance): CKEditor 5 is a large established publisher; lack of Sigstore provenance is consistent across all their releases and not a risk indicator. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 48.2.0 | 6 / 0 | |
| 48.1.1 | 6 / 0 | |
| 48.1.0 | 6 / 0 | |
| 48.0.1 | 6 / 0 | |
| 48.0.0 | 6 / 0 | |
| 47.7.2 | 6 / 0 | |
| 47.7.1 | 6 / 0 | |
| 47.7.0 | 6 / 0 | |
| 47.6.2 | 6 / 0 | |
| 47.6.1 | 6 / 0 | |
| 47.6.0 | 6 / 0 | |
| 47.5.0 | 6 / 0 | |
| 47.4.0 | 6 / 0 | |
| 47.3.0 | 6 / 0 | |
| 47.2.0 | 6 / 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. 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. 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.