@progress/kendo-angular-editor SEE LICENSE IN LICENSE.md 23 versions

@progress/kendo-angular-editor

npm Homepage

Kendo UI Editor for Angular

23

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

progress

Keywords

AngularKendo UI

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
dependencies	unvetted-dep:@progress/kendo-editor-common	AI (dependencies): Same Progress org scope; part of the established Kendo UI for Angular suite.	ai	2026/05/04
phantom-deps	phantom-dep:tslib	AI (phantom-deps): tslib is a well-known implicit Angular/TypeScript runtime dep; stable false positive for this package.	ai	2026/04/29
phantom-deps	phantom-dep:@progress/kendo-angular-schematics	AI (phantom-deps): Schematics dep is referenced via schematics collection.json, not direct imports; stable false positive for this package.	ai	2026/04/29

Versions (showing 23 of 23)

Version	Deps	Published
24.1.0	3 / 0	2026-06-04
24.0.3	3 / 0	2026-05-29
24.0.2	3 / 0	2026-05-28
24.0.1	3 / 0	2026-05-21
24.0.0	3 / 0	2026-05-20
23.4.0	3 / 0	2026-04-24
23.3.0	3 / 0	2026-04-02
23.2.2	3 / 0	2026-03-18
23.2.1	3 / 0	2026-03-17
23.2.0	3 / 0	2026-02-27
23.1.0	3 / 0	2026-02-18
23.0.1	3 / 0	2026-02-11
23.0.0	3 / 0	2026-02-10
22.0.1	3 / 0	2026-01-15
22.0.0	3 / 0	2026-01-14
21.4.1	3 / 0	2026-01-14
21.4.0	3 / 0	2026-01-12
21.3.0	3 / 0	2025-12-11
21.2.0	3 / 0	2025-12-03
21.1.0	3 / 0	2025-11-20
21.0.1	3 / 0	2025-11-19
21.0.0	3 / 0	2025-11-12
20.1.2	3 / 0	2025-11-28

v24.1.0

1 finding

LOW No provenance attestation provenance

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

v24.0.3

1 finding

LOW No provenance attestation provenance

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

v24.0.2

1 finding

LOW No provenance attestation provenance

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

v24.0.1

1 finding

LOW No provenance attestation provenance

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

v24.0.0

1 finding

LOW No provenance attestation provenance

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

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

v23.2.2

1 finding

LOW No provenance attestation provenance

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

v23.2.1

1 finding

LOW No provenance attestation provenance

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

v23.2.0

1 finding

LOW No provenance attestation provenance

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

v23.1.0

1 finding

LOW No provenance attestation provenance

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

v23.0.1

1 finding

LOW No provenance attestation provenance

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

v23.0.0

1 finding

LOW No provenance attestation provenance

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

v22.0.1

1 finding

LOW No provenance attestation provenance

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

v22.0.0

1 finding

LOW No provenance attestation provenance

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

v21.4.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.

v21.4.0

1 finding

LOW No provenance attestation provenance

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

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

v21.2.0

1 finding

LOW No provenance attestation provenance

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

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

v21.0.1

1 finding

LOW No provenance attestation provenance

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

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

v20.1.2

1 finding

LOW No provenance attestation provenance

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