@ckeditor/ckeditor5-build-inline
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:build/translations/hy.js | AI (source-diff): Minified i18n dictionary, not obfuscated code; standard CKEditor build artifact. | ai | |
| source-diff | obfuscated-file:build/translations/kk.js | AI (source-diff): Minified i18n dictionary, not obfuscated code; standard CKEditor build artifact. | ai | |
| source-diff | obfuscated-file:build/translations/ti.js | AI (source-diff): Minified i18n dictionary, not obfuscated code; standard CKEditor build artifact. | ai |
v44.3.0
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.
v39.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.