@progress/kendo-angular-charts No license 20 versions

@progress/kendo-angular-charts

npm Homepage

20

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

progress

Keywords

AngularChartsData VisualizationDataVizKendo UIProgressArea ChartBar ChartBox Plot ChartBullet ChartHeatmap ChartLine ChartRadar ChartRange Area ChartRange Bar ChartWaterfall ChartDonut ChartPie ChartFunnel ChartPyramid ChartBubble ChartPolar ChartScatter Plot ChartStock ChartSparklineAngular-chartsAngular-graphs

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
dependencies	unvetted-dep:@progress/kendo-svg-icons	AI (dependencies): Same org (@progress) dependency from established Progress/Telerik publisher; stable pattern across all kendo-angular versions.	ai	2026/05/04
phantom-deps	phantom-dep:tslib	AI (phantom-deps): tslib is a known implicit Angular/TypeScript runtime dep; stable false positive for this package.	ai	2026/04/30
phantom-deps	phantom-dep:@progress/kendo-angular-schematics	AI (phantom-deps): Schematics dep referenced via schematics collection.json, not direct import; stable false positive.	ai	2026/04/30

Versions (showing 20 of 20)

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

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.4.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. Only ~12% of npm packages have provenance, so this is common but not ideal.

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

v21.1.0

1 finding

LOW No provenance attestation provenance

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

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.