← Home

@ckeditor/ckeditor5-editor-decoupled

npm Repository Homepage

Decoupled 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.

SourceRuleReasonAccepted byWhen
source-diff obfuscated-file:build/editor-decoupled.js AI (source-diff): build/editor-decoupled.js is CKEditor5's standard webpack DLL bundle output — minified but not obfuscated, contains recognizable CKEditor class names and webpack boilerplate. Expected artifact for this package. ai
publish-pattern new-deps-added AI (publish-pattern): The added 'ckeditor5' dependency is the official CKEditor5 umbrella package from the same publisher (CKSource), at the same matching version. Not a suspicious third-party dependency. ai
dependencies unvetted-dep:@ckeditor/ckeditor5-ui AI (dependencies): First-party CKEditor 5 sibling package from the same monorepo release; not a third-party unknown. ai
dependencies unvetted-dep:@ckeditor/ckeditor5-core AI (dependencies): First-party CKEditor 5 sibling package from the same monorepo release; not a third-party unknown. ai
dependencies unvetted-dep:@ckeditor/ckeditor5-utils AI (dependencies): First-party CKEditor 5 sibling package from the same monorepo release; not a third-party unknown. ai
dependencies unvetted-dep:@ckeditor/ckeditor5-engine AI (dependencies): First-party CKEditor 5 sibling package from the same monorepo release; not a third-party unknown. ai

Versions (showing 15 of 15)

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
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
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-decoupled.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

2 findings
HIGH New obfuscated file: build/editor-decoupled.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.6.2

2 findings
HIGH New obfuscated file: build/editor-decoupled.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.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.