@ckeditor/ckeditor5-autosave
Autosave feature 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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:build/autosave.js | AI (source-diff): Standard webpack minified build output for CKEditor5 autosave plugin; no suspicious patterns, just normal bundled JS. | ai | |
| phantom-deps | phantom-dep:@ckeditor/ckeditor5-engine | AI (phantom-deps): Same-org sibling dependency declared but not directly imported; consistent with CKEditor 5 monorepo packaging patterns across all versions. | ai | |
| provenance | no-provenance | AI (provenance): CKEditor is an established publisher with 1575 versions and 765k weekly downloads; lack of Sigstore provenance is not a concern for this package. | ai | |
| license | uncommon-license:SEE LICENSE IN LICENSE.md | AI (license): Standard CKEditor 5 license declaration used consistently across all their packages; not a security issue. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 48.3.1 | 4 / 0 | |
| 48.3.0 | 4 / 0 | |
| 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 | |
| 47.7.3 | 4 / 0 | |
| 47.7.2 | 4 / 0 | |
| 47.7.1 | 4 / 0 | |
| 47.7.0 | 4 / 0 | |
| 47.6.2 | 4 / 0 | |
| 47.6.1 | 4 / 0 | |
| 47.6.0 | 4 / 0 | |
| 47.5.0 | 4 / 0 | |
| 47.4.0 | 4 / 0 | |
| 47.3.0 | 4 / 0 | |
| 47.2.0 | 4 / 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.