@progress/kendo-svg-icons
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Progress/Telerik migrated publishing to GitHub Actions CI/CD with SLSA attestation; stable pattern for this package going forward. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 5.4.0 | 0 / 3 | |
| 5.3.0 | 0 / 3 | |
| 5.2.0 | 0 / 3 | |
| 5.1.0 | 0 / 3 | |
| 5.0.0 | 0 / 3 | |
| 4.11.0 | 0 / 3 | |
| 4.10.1 | 0 / 3 | |
| 4.10.0 | 0 / 3 | |
| 4.9.3 | 0 / 3 | |
| 4.9.2 | 0 / 3 | |
| 4.9.1 | 0 / 3 | |
| 4.9.0 | 0 / 3 | |
| 4.8.0 | 0 / 3 | |
| 4.7.0 | 0 / 3 | |
| 4.6.2 | 0 / 3 | |
| 4.6.1 | 0 / 3 | |
| 4.6.0 | 0 / 3 | |
| 4.5.0 | 0 / 3 | |
| 4.4.0 | 0 / 3 | |
| 4.3.0 | 0 / 3 | |
| 4.2.0 | 0 / 3 | |
| 4.1.0 | 0 / 3 | |
| 4.0.0 | 0 / 3 |
v5.4.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.11.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.10.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.10.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.9.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.