@ckeditor/ckeditor5-editor-multi-root SEE LICENSE IN LICENSE.md 15 versions

@ckeditor/ckeditor5-editor-multi-root

npm Repository Homepage

Multi-root editor implementation for CKEditor 5.

15

Versions

SEE LICENSE IN LICENSE.md

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

ckeditor

Keywords

ckeditorckeditor5ckeditor 5ckeditor5-editor

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	obfuscated-file:build/editor-multi-root.js	AI (source-diff): Standard webpack DLL bundle for CKEditor 5; minified build output, not obfuscation. Expected for all CKEditor packages shipping build/ directory.	ai	2026/04/26
license	uncommon-license:SEE LICENSE IN LICENSE.md	AI (license): CKEditor's standard dual GPL/commercial license reference. Well-known licensing model for this package family.	ai	2026/04/26
dependencies	unvetted-dep:@ckeditor/ckeditor5-ui	AI (dependencies): First-party CKEditor 5 sibling package published in lockstep from the same monorepo; consistently present across all versions.	ai	2026/04/25
dependencies	unvetted-dep:@ckeditor/ckeditor5-core	AI (dependencies): First-party CKEditor 5 sibling package published in lockstep from the same monorepo; consistently present across all versions.	ai	2026/04/25
dependencies	unvetted-dep:@ckeditor/ckeditor5-utils	AI (dependencies): First-party CKEditor 5 sibling package published in lockstep from the same monorepo; consistently present across all versions.	ai	2026/04/25
dependencies	unvetted-dep:@ckeditor/ckeditor5-engine	AI (dependencies): First-party CKEditor 5 sibling package published in lockstep from the same monorepo; consistently present across all versions.	ai	2026/04/25

Versions (showing 15 of 15)

Version	Deps	Published
48.2.0	5 / 0	2026-06-02
48.1.1	5 / 0	2026-05-18
48.1.0	5 / 0	2026-05-13
48.0.1	5 / 0	2026-04-22
48.0.0	5 / 0	2026-03-31
47.7.2	6 / 0	2026-05-18
47.7.1	6 / 0	2026-04-23
47.7.0	6 / 0	2026-04-16
47.6.2	6 / 0	2026-04-08
47.6.1	6 / 0	2026-03-11
47.6.0	6 / 0	2026-03-04
47.5.0	6 / 0	2026-02-11
47.4.0	6 / 0	2026-01-14
47.3.0	6 / 0	2025-12-03
47.2.0	6 / 0	2025-11-05

v48.2.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v48.1.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v48.1.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v48.0.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v48.0.0

1 finding

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v47.7.1

2 findings

HIGH New obfuscated file: build/editor-multi-root.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v47.7.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v47.6.2

1 finding

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v47.6.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v47.5.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v47.4.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v47.3.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v47.2.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.