@ckeditor/ckeditor5-remove-format SEE LICENSE IN LICENSE.md 15 versions

@ckeditor/ckeditor5-remove-format

npm Repository Homepage

Remove format feature for CKEditor 5.

15

Versions

SEE LICENSE IN LICENSE.md

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

ckeditor

Keywords

ckeditorckeditor5ckeditor 5ckeditor5-featureckeditor5-plugin

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
publish-pattern	new-deps-added	AI (publish-pattern): CKEditor5 consolidated individual @ckeditor/* packages into the umbrella 'ckeditor5' package; this dependency change is part of documented architectural restructuring, not suspicious injection.	ai	2026/04/26
dependencies	unvetted-dep:@ckeditor/ckeditor5-core	AI (dependencies): Sibling CKEditor5 monorepo package, always released at the same version. Not a third-party or suspicious dependency.	ai	2026/04/25
dependencies	unvetted-dep:@ckeditor/ckeditor5-icons	AI (dependencies): Sibling CKEditor5 monorepo package, always released at the same version. Not a third-party or suspicious dependency.	ai	2026/04/25
dependencies	unvetted-dep:@ckeditor/ckeditor5-ui	AI (dependencies): Sibling CKEditor5 monorepo package, always released at the same version. Not a third-party or suspicious dependency.	ai	2026/04/25
dependencies	unvetted-dep:@ckeditor/ckeditor5-engine	AI (dependencies): Sibling CKEditor5 monorepo package, always released at the same version. Not a third-party or suspicious dependency.	ai	2026/04/25
license	uncommon-license:SEE LICENSE IN LICENSE.md	AI (license): Standard CKEditor5 license declaration referencing their well-known commercial/open-source dual-license model. Stable across all CKEditor5 packages.	ai	2026/04/25
dependencies	unvetted-dep:@ckeditor/ckeditor5-utils	AI (dependencies): Sibling CKEditor5 monorepo package, always released at the same version. Not a third-party or suspicious dependency.	ai	2026/04/25

Versions (showing 15 of 15)

Version	Deps	Published
48.2.0	5 / 0	2026-06-02
48.1.1	5 / 0	2026-05-18
48.1.0	5 / 0	2026-05-13
48.0.1	5 / 0	2026-04-22
48.0.0	5 / 0	2026-03-31
47.7.2	5 / 0	2026-05-18
47.7.1	5 / 0	2026-04-23
47.7.0	5 / 0	2026-04-16
47.6.2	5 / 0	2026-04-08
47.6.1	5 / 0	2026-03-11
47.6.0	5 / 0	2026-03-04
47.5.0	5 / 0	2026-02-11
47.4.0	5 / 0	2026-01-14
47.3.0	5 / 0	2025-12-03
47.2.0	5 / 0	2025-11-05

v48.2.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v48.1.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v48.1.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v48.0.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v48.0.0

1 finding

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v47.7.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v47.7.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v47.6.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v47.6.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v47.6.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v47.5.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v47.4.0

1 finding

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.