@ckeditor/ckeditor5-paste-from-office
Paste from Office 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 | large-new-source-files | AI (source-diff): CKEditor packages ship dist/build/src directories as standard; file count differences are due to cross-branch version comparison. | ai | |
| source-diff | obfuscated-file:build/paste-from-office.js | AI (source-diff): Standard CKEditor webpack DLL bundle output with proper copyright header; not obfuscation. Stable pattern for this package. | 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-core | AI (dependencies): Sibling CKEditor 5 monorepo package; unvetted status reflects review pipeline lag, not a real risk for this well-established publisher. | ai | |
| dependencies | unvetted-dep:@ckeditor/ckeditor5-engine | AI (dependencies): Sibling CKEditor 5 monorepo package; unvetted status reflects review pipeline lag, not a real risk for this well-established publisher. | ai | |
| dependencies | unvetted-dep:@ckeditor/ckeditor5-clipboard | AI (dependencies): Sibling CKEditor 5 monorepo package; unvetted status reflects review pipeline lag, not a real risk for this well-established publisher. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 48.2.0 | 4 / 0 | |
| 48.1.1 | 3 / 0 | |
| 48.1.0 | 3 / 0 | |
| 48.0.1 | 3 / 0 | |
| 48.0.0 | 3 / 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.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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v47.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.