@ckeditor/ckeditor5-autoformat
Autoformatting feature for CKEditor 5.
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:build/autoformat.js | AI (source-diff): Standard webpack/CKEditor DLL minified build output; consistent pattern across all @ckeditor packages. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Build/dist artifacts are standard for @ckeditor packages; file count reflects normal bundled output. | ai | |
| license | uncommon-license:SEE LICENSE IN LICENSE.md | AI (license): CKEditor's standard dual GPL/commercial license reference; stable across all @ckeditor packages. | ai | |
| dependencies | unvetted-dep:@ckeditor/ckeditor5-typing | AI (dependencies): Same-org monorepo dependency; all @ckeditor/ckeditor5-* packages are released together at matching versions by CKSource. | ai | |
| dependencies | unvetted-dep:@ckeditor/ckeditor5-core | AI (dependencies): Same-org monorepo dependency; all @ckeditor/ckeditor5-* packages are released together at matching versions by CKSource. | ai | |
| phantom-deps | phantom-dep:@ckeditor/ckeditor5-heading | AI (phantom-deps): Same-org scope; declared as a runtime peer/plugin dependency without direct import is a normal CKEditor 5 monorepo pattern. | ai | |
| dependencies | unvetted-dep:@ckeditor/ckeditor5-heading | AI (dependencies): Same-org monorepo dependency; all @ckeditor/ckeditor5-* packages are released together at matching versions by CKSource. | ai | |
| dependencies | unvetted-dep:@ckeditor/ckeditor5-utils | AI (dependencies): Same-org monorepo dependency; all @ckeditor/ckeditor5-* packages are released together at matching versions by CKSource. | ai | |
| dependencies | unvetted-dep:@ckeditor/ckeditor5-engine | AI (dependencies): Same-org monorepo dependency; all @ckeditor/ckeditor5-* packages are released together at matching versions by CKSource. | 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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v48.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v48.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v48.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v48.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v47.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v47.7.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v47.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v47.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v47.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v47.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v47.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v47.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v47.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v47.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.