@progress/kendo-editor-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
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 1.12.6 | 14 / 20 | |
| 1.12.5 | 14 / 0 | |
| 1.12.4 | 14 / 0 | |
| 1.12.3 | 14 / 0 | |
| 1.11.9 | 14 / 21 | |
| 1.11.8 | 14 / 21 | |
| 1.11.7 | 14 / 21 | |
| 1.11.6 | 13 / 21 | |
| 1.11.5 | 13 / 21 | |
| 1.11.4 | 13 / 21 |
v1.12.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.