@ckeditor/ckeditor5-indent
Block indentation 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/indent.js | AI (source-diff): Standard webpack build bundle for CKEditor plugin; contains CSS and translation strings, not obfuscated malware. | ai | |
| source-diff | large-new-source-files | AI (source-diff): CKEditor packages ship build/dist directories with bundled output; large file count is expected for this package structure. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Adding ckeditor5 umbrella dep is part of CKEditor's monorepo restructuring; all deps are within the CKEditor ecosystem. | ai | |
| phantom-deps | phantom-dep:@ckeditor/ckeditor5-heading | AI (phantom-deps): Declared sibling dependency in a monorepo; not directly imported but part of the coordinated CKEditor 5 release. Not a security concern. | ai | |
| provenance | no-provenance | AI (provenance): CKEditor 5 is a long-established package; lack of Sigstore provenance is common and not a risk signal for this publisher. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 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.2 | 8 / 0 | |
| 47.7.1 | 8 / 0 | |
| 47.7.0 | 8 / 0 | |
| 47.6.2 | 8 / 0 | |
| 47.6.1 | 8 / 0 | |
| 47.6.0 | 8 / 0 | |
| 47.5.0 | 8 / 0 | |
| 47.4.0 | 8 / 0 | |
| 47.3.0 | 8 / 0 | |
| 47.2.0 | 8 / 0 |
v48.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v48.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v48.1.0
1 finding[Accepted risk] Package 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 finding[Accepted risk] 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[Accepted risk] Package 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v47.7.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v47.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v47.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v47.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v47.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v47.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v47.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v47.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.