← Home

@ckeditor/ckeditor5-ckfinder

CKFinder integration for CKEditor 5.

18
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

ckeditor

Keywords

ckeditorckeditor5ckeditor 5ckeditor5-featureckeditor5-plugin

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff obfuscated-file:build/ckfinder.js AI (source-diff): Standard webpack minified build output for CKEditor plugin; contains translation dictionaries and module loader boilerplate, not obfuscation. ai
source-diff large-new-source-files AI (source-diff): CKEditor monorepo package restructuring adds dist/build/lang files; expected for this ecosystem. ai
phantom-deps phantom-dep:@ckeditor/ckeditor5-image AI (phantom-deps): Sibling @ckeditor package declared as a dependency in package.json; phantom-dep flag is a false positive for this monorepo plugin package. ai
provenance no-provenance AI (provenance): CKEditor5 is a major, long-established project; lack of Sigstore provenance is not a risk signal for this publisher. ai

Versions (showing 18 of 18)

Version Deps Published
48.3.1 7 / 0
48.3.0 7 / 0
48.2.0 7 / 0
48.1.1 7 / 0
48.1.0 7 / 0
48.0.1 7 / 0
48.0.0 7 / 0
47.7.3 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.3.1

1 finding
INFO No provenance attestation provenance

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

v48.3.0

1 finding
INFO No provenance attestation provenance

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

v47.7.3

1 finding
INFO No provenance attestation provenance

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