@progress/kendo-font-icons
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 5.0.0 | 0 / 0 | |
| 4.9.2 | 0 / 0 | |
| 4.9.1 | 0 / 0 | |
| 4.9.0 | 0 / 0 | |
| 4.8.0 | 0 / 0 | |
| 4.7.0 | 0 / 0 | |
| 4.6.2 | 0 / 0 | |
| 4.6.1 | 0 / 0 | |
| 4.6.0 | 0 / 0 | |
| 4.5.0 | 0 / 0 | |
| 4.4.0 | 0 / 0 | |
| 4.3.0 | 0 / 0 | |
| 4.2.0 | 0 / 0 |
v5.0.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.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.9.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.9.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.