@progress/kendo-react-charts
React Chart renders a wide range of high-quality data visualizations. KendoReact Charts package
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established commercial package from Progress/Telerik; provenance absence is consistent across all their releases. | ai | |
| dependencies | unvetted-dep:@progress/kendo-charts | AI (dependencies): Same vendor (@progress) dependency; stable pattern across all KendoReact chart package versions. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 15.0.0 | 2 / 0 | |
| 14.4.1 | 2 / 0 | |
| 14.4.0 | 2 / 0 | |
| 14.3.2 | 2 / 0 | |
| 14.3.1 | 2 / 0 | |
| 14.3.0 | 2 / 0 | |
| 14.2.1 | 2 / 0 | |
| 14.2.0 | 2 / 0 | |
| 14.1.1 | 2 / 0 | |
| 14.1.0 | 2 / 0 | |
| 14.0.1 | 2 / 0 | |
| 14.0.0 | 2 / 0 | |
| 13.3.0 | 2 / 0 | |
| 13.2.0 | 2 / 0 | |
| 13.1.0 | 2 / 0 | |
| 13.0.0 | 2 / 0 |
v15.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.