@progress/kendo-react-editor
React Editor enables users to create rich text content through a WYSIWYG interface. KendoReact Editor package
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:config/defaultStyles.d.ts | AI (source-diff): Long line is a CSS string literal in a .d.ts export constant — not obfuscated, stable pattern for this package. | ai | |
| dependencies | unvetted-dep:@progress/kendo-editor-common | AI (dependencies): Sibling Progress/Telerik package; same vendor suite, stable pattern across all KendoReact versions. | ai | |
| dependencies | unvetted-peer-dep:@progress/kendo-drawing | AI (dependencies): Progress/Telerik peer dep; consistent across all KendoReact releases. | ai | |
| dependencies | unvetted-peer-dep:@progress/kendo-licensing | AI (dependencies): Progress/Telerik peer dep; consistent across all KendoReact releases. | ai | |
| dependencies | unvetted-peer-dep:@progress/kendo-svg-icons | AI (dependencies): Progress/Telerik peer dep; consistent across all KendoReact releases. | ai | |
| provenance | no-provenance | AI (provenance): Large commercial publisher; provenance absence is consistent across all KendoReact packages and not a risk indicator here. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 15.0.0 | 2 / 0 | |
| 14.4.1 | 2 / 0 | |
| 14.4.0 | 2 / 0 | |
| 14.3.2 | 2 / 0 | |
| 14.3.1 | 2 / 0 | |
| 14.3.0 | 2 / 0 | |
| 14.2.1 | 2 / 0 | |
| 14.2.0 | 2 / 0 | |
| 14.1.1 | 2 / 0 | |
| 14.1.0 | 2 / 0 | |
| 14.0.1 | 2 / 0 | |
| 14.0.0 | 2 / 0 | |
| 13.3.0 | 2 / 0 | |
| 13.2.0 | 2 / 0 | |
| 13.1.0 | 2 / 0 | |
| 13.0.0 | 2 / 0 |
v15.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.3.2
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.3.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.2.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.2.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.1.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.1.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.0.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.0.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.