@ckeditor/ckeditor5-adapter-ckfinder
CKFinder adapter 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.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@ckeditor/ckeditor5-utils | AI (phantom-deps): Same-org monorepo package; declaring transitive deps explicitly is a known pattern for CKEditor 5 packages. Not a risk. | ai | |
| provenance | no-provenance | AI (provenance): Established CKEditor 5 package with 670k weekly downloads and 1584 versions; lack of Sigstore provenance is not a risk signal here. | ai | |
| license | uncommon-license:SEE LICENSE IN LICENSE.md | AI (license): Standard CKEditor 5 license expression referencing their well-documented commercial/open-source dual license. Stable across all CKEditor 5 packages. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 48.3.1 | 3 / 0 | |
| 48.3.0 | 3 / 0 | |
| 48.2.0 | 3 / 0 | |
| 48.1.1 | 3 / 0 | |
| 48.1.0 | 3 / 0 | |
| 48.0.1 | 3 / 0 | |
| 48.0.0 | 3 / 0 | |
| 47.7.3 | 3 / 0 | |
| 47.7.2 | 3 / 0 | |
| 47.7.1 | 3 / 0 | |
| 47.7.0 | 3 / 0 | |
| 47.6.2 | 3 / 0 | |
| 47.6.1 | 3 / 0 | |
| 47.6.0 | 3 / 0 | |
| 47.5.0 | 3 / 0 | |
| 47.4.0 | 3 / 0 | |
| 47.3.0 | 3 / 0 | |
| 47.2.0 | 3 / 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.