@progress/kendo-drawing
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 Progress/Telerik package; provenance absence is consistent across all their releases. | ai | |
| license | uncommon-license:See license in LICENSE.md | AI (license): Standard commercial Telerik license; stable across all versions of this package. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 1.25.2 | 2 / 14 | |
| 1.25.1 | 2 / 14 | |
| 1.25.0 | 2 / 14 | |
| 1.24.1 | 2 / 14 | |
| 1.24.0 | 2 / 14 | |
| 1.23.1 | 2 / 15 | |
| 1.23.0 | 2 / 15 | |
| 1.22.2 | 2 / 15 | |
| 1.22.1 | 2 / 15 | |
| 1.22.0 | 2 / 15 |
v1.25.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.24.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.24.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.
v1.23.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.23.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.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.