@ckeditor/ckeditor5-dev-utils No license 32 versions

@ckeditor/ckeditor5-dev-utils

npm Repository Homepage

32

Versions

—

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

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:postcss-loader	AI (phantom-deps): PostCSS loader referenced in config generation code, not directly imported.	ai	2026/05/24
phantom-deps	phantom-dep:@types/postcss-import	AI (phantom-deps): Type-only package loaded by convention; stable false positive for this package.	ai	2026/05/24
phantom-deps	phantom-dep:raw-loader	AI (phantom-deps): Webpack loader declared and used in build configs; stable for build-tool packages.	ai	2026/05/23
phantom-deps	phantom-dep:babel-loader	AI (phantom-deps): Webpack loader declared and used in build configs; stable for build-tool packages.	ai	2026/05/23
phantom-deps	phantom-dep:mocha	AI (phantom-deps): Test framework declared and used in test configs; stable pattern for dev-utils.	ai	2026/05/23
phantom-deps	phantom-dep:esbuild-loader	AI (phantom-deps): Webpack loader declared and used in build configs; stable for build-tool packages.	ai	2026/05/23
phantom-deps	phantom-dep:@types/through2	AI (phantom-deps): TypeScript types for through2; convention-loaded by framework; stable for this package.	ai	2026/05/23
phantom-deps	phantom-dep:style-loader	AI (phantom-deps): Webpack loader declared and used in build configs; stable for build-tool packages.	ai	2026/05/23
phantom-deps	phantom-dep:css-loader	AI (phantom-deps): Webpack loader declared and used in build configs; stable for build-tool packages.	ai	2026/05/23

Versions (showing 32 of 32)

Version	Deps	Published
56.1.0	18 / 0	2026-06-02
56.0.0	18 / 0	2026-05-29
55.6.3	17 / 0	2026-05-27
55.6.2	17 / 0	2026-05-27
55.6.1	17 / 0	2026-05-21
55.6.0	18 / 0	2026-05-15
55.5.0	18 / 0	2026-04-09
55.4.0	18 / 0	2026-04-03
55.3.1	18 / 0	2026-04-01
55.3.0	18 / 0	2026-03-27
55.2.0	18 / 0	2026-03-19
55.1.1	18 / 0	2026-03-19
55.1.0	18 / 0	2026-03-18
55.0.0	18 / 0	2026-03-12
54.7.3	26 / 0	2026-05-27
54.7.2	26 / 0	2026-05-15
54.7.1	26 / 0	2026-04-01
54.7.0	26 / 0	2026-03-27
54.6.1	26 / 0	2026-03-19
54.6.0	26 / 0	2026-03-18
54.5.0	26 / 0	2026-03-12
54.4.0	26 / 0	2026-03-11
54.3.4	26 / 0	2026-02-11
54.3.3	26 / 0	2026-02-03
54.3.2	26 / 0	2026-01-21
54.3.1	26 / 0	2026-01-20
54.3.0	26 / 0	2026-01-13
54.2.3	26 / 0	2025-12-22
54.2.2	26 / 0	2025-12-15
54.2.1	26 / 0	2025-12-03
54.2.0	26 / 0	2025-11-26
54.1.0	26 / 0	2025-11-20

v56.1.0

1 finding

LOW No provenance attestation provenance

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

v56.0.0

1 finding

LOW No provenance attestation provenance

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

v55.6.3

1 finding

LOW No provenance attestation provenance

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

v55.6.2

1 finding

LOW No provenance attestation provenance

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

v55.6.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.

v55.6.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.

v55.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.

v55.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.

v55.3.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.

v55.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.

v55.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.

v55.1.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.

v55.1.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.

v55.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.

v54.7.3

1 finding

LOW No provenance attestation provenance

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

v54.7.2

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.

v54.7.1

1 finding

LOW No provenance attestation provenance

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

v54.7.0

1 finding

LOW No provenance attestation provenance

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

v54.6.1

1 finding

LOW No provenance attestation provenance

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

v54.6.0

1 finding

LOW No provenance attestation provenance

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

v54.5.0

1 finding

LOW No provenance attestation provenance

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

v54.4.0

1 finding

LOW No provenance attestation provenance

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

v54.3.4

1 finding

LOW No provenance attestation provenance

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

v54.3.3

1 finding

LOW No provenance attestation provenance

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

v54.3.2

1 finding

LOW No provenance attestation provenance

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

v54.3.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.

v54.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.

v54.2.3

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.

v54.2.2

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.

v54.2.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.

v54.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.

v54.1.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.