@ckeditor/ckeditor5-export-inline-styles
The export with inline styles 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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:specificity | AI (phantom-deps): specificity is a legitimate CSS utility library; phantom detection reflects indirect usage patterns common in CKEditor plugin packages. | ai | |
| phantom-deps | phantom-dep:@ckeditor/ckeditor5-utils | AI (phantom-deps): Same-org CKEditor dependency; phantom detection reflects indirect usage common across the CKEditor5 plugin ecosystem. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 48.2.0 | 4 / 0 | |
| 48.1.1 | 4 / 0 | |
| 48.1.0 | 4 / 0 | |
| 48.0.1 | 4 / 0 | |
| 48.0.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.