@ckeditor/ckeditor5-alignment
Text alignment 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/alignment.js | AI (source-diff): Standard webpack/rollup minified build output for CKEditor DLL plugin; not obfuscation. Stable for this package. | ai | |
| source-diff | large-new-source-files | AI (source-diff): CKEditor packages ship build/, dist/, lang/, theme/ directories with many files; expected for this package. | ai | |
| dependencies | unvetted-dep:@ckeditor/ckeditor5-utils | AI (dependencies): Sibling CKEditor 5 monorepo package from the same publisher; unvetted status is a pipeline artifact, not a real risk. | ai | |
| dependencies | unvetted-dep:@ckeditor/ckeditor5-engine | AI (dependencies): Sibling CKEditor 5 monorepo package from the same publisher; unvetted status is a pipeline artifact, not a real risk. | ai | |
| dependencies | unvetted-dep:@ckeditor/ckeditor5-ui | AI (dependencies): Sibling CKEditor 5 monorepo package from the same publisher; unvetted status is a pipeline artifact, not a real risk. | ai | |
| license | uncommon-license:SEE LICENSE IN LICENSE.md | AI (license): Standard CKEditor licensing declaration (GPL/commercial dual-license); well-known and expected for this publisher across all versions. | ai | |
| phantom-deps | phantom-dep:@ckeditor/ckeditor5-engine | AI (phantom-deps): Same-org sibling dep declared for version alignment in the CKEditor 5 monorepo; not a real phantom dependency concern. | ai | |
| dependencies | unvetted-dep:@ckeditor/ckeditor5-core | AI (dependencies): Sibling CKEditor 5 monorepo package from the same publisher; unvetted status is a pipeline artifact, not a real risk. | 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 | 5 / 0 | |
| 47.7.1 | 5 / 0 | |
| 47.7.0 | 5 / 0 | |
| 47.6.2 | 5 / 0 | |
| 47.6.1 | 5 / 0 | |
| 47.6.0 | 5 / 0 | |
| 47.5.0 | 5 / 0 | |
| 47.4.0 | 5 / 0 | |
| 47.3.0 | 5 / 0 | |
| 47.2.0 | 5 / 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
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.6.2
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.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.