@progress/kendo-spreadsheet-common
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
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 to GitHub Actions CI publishing; consistent with org-wide automation rollout across their npm packages. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 1.2.13 | 0 / 17 | |
| 1.2.12 | 0 / 17 | |
| 1.2.11 | 0 / 17 | |
| 1.2.10 | 0 / 17 | |
| 1.2.9 | 0 / 18 | |
| 1.2.8 | 0 / 17 | |
| 1.2.7 | 0 / 17 | |
| 1.2.6 | 0 / 17 | |
| 1.2.5 | 0 / 16 | |
| 1.2.4 | 0 / 16 | |
| 1.2.3 | 0 / 16 | |
| 1.2.2 | 0 / 16 | |
| 1.2.1 | 0 / 16 | |
| 1.2.0 | 0 / 16 | |
| 1.1.2 | 0 / 13 |
v1.2.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.