@progress/kendo-angular-intl
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a known implicit dependency; stable for this package. | ai | |
| phantom-deps | phantom-dep:@progress/kendo-intl | AI (phantom-deps): Internal @progress-scoped dependency; stable organizational pattern. | ai | |
| phantom-deps | phantom-dep:@progress/kendo-angular-schematics | AI (phantom-deps): Internal @progress-scoped dependency; stable organizational pattern. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 24.0.3 | 3 / 0 | |
| 24.0.2 | 3 / 0 | |
| 24.0.1 | 3 / 0 | |
| 23.4.0 | 3 / 0 |
v24.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.