@ckeditor/ckeditor5-operations-compressor
CKEditor 5 operations compressor for real-time collaboration.
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:protobufjs | AI (dependencies): protobufjs is a legitimate, widely-used library; its use in a real-time collaboration operations compressor for serializing OT data is expected and appropriate. | ai | |
| phantom-deps | phantom-dep:es-toolkit | AI (phantom-deps): Package ships pre-built dist output (obfuscated:true); es-toolkit is bundled into dist rather than imported at runtime, making phantom-dep detection a stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:protobufjs | AI (phantom-deps): Package ships pre-built dist output; protobufjs is bundled into dist rather than imported at runtime, making phantom-dep detection a stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@ckeditor/ckeditor5-utils | AI (dependencies): First-party CKEditor dependency from the same org; legitimate and expected for all @ckeditor/ckeditor5-* packages. | ai | |
| dependencies | unvetted-dep:@ckeditor/ckeditor5-engine | AI (dependencies): First-party CKEditor dependency from the same org; legitimate and expected for all @ckeditor/ckeditor5-* packages. | ai | |
| phantom-deps | phantom-dep:@ckeditor/ckeditor5-utils | AI (phantom-deps): Same-org first-party dependency; phantom detection is expected in CKEditor monorepo build configurations. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 48.2.0 | 4 / 0 | |
| 48.1.1 | 4 / 0 | |
| 48.1.0 | 4 / 0 | |
| 48.0.1 | 4 / 0 | |
| 48.0.0 | 4 / 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.