@syncfusion/ej2-richtexteditor
Essential JS 2 RichTextEditor component
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): First-party Syncfusion sibling packages pinned to same version; normal monorepo pattern. | ai | |
| source-diff | large-new-source-files | AI (source-diff): New files are feature source for added sibling deps, not injected/bundled code. | ai | |
| license | uncommon-license:SEE LICENSE IN license | AI (license): Standard Syncfusion commercial license format; stable across all their packages. | ai | |
| dependencies | unvetted-dep:@syncfusion/ej2-buttons | AI (dependencies): Same-org sibling package; version-pinned to matching release band. | ai | |
| dependencies | unvetted-dep:@syncfusion/ej2-dropdowns | AI (dependencies): Same-org sibling package; version-pinned to matching release band. | ai | |
| dependencies | unvetted-dep:@syncfusion/ej2-filemanager | AI (dependencies): Same-org sibling package; version-pinned to matching release band. | ai | |
| dependencies | unvetted-dep:@syncfusion/ej2-navigations | AI (dependencies): Same-org sibling package; version-pinned to matching release band. | ai | |
| dependencies | unvetted-dep:@syncfusion/ej2-base | AI (dependencies): Same-org sibling package; version-pinned to matching release band. | ai | |
| dependencies | unvetted-dep:@syncfusion/ej2-interactive-chat | AI (dependencies): Same-org sibling package; version-pinned to matching release band. | ai | |
| dependencies | unvetted-dep:@syncfusion/ej2-markdown-converter | AI (dependencies): Same-org sibling package; version-pinned to matching release band. | ai | |
| provenance | no-provenance | AI (provenance): Syncfusion does not publish with Sigstore provenance; consistent across their entire package ecosystem. | ai | |
| dependencies | unvetted-dep:@syncfusion/ej2-splitbuttons | AI (dependencies): Same-org sibling package; version-pinned to matching release band. | ai | |
| dependencies | unvetted-dep:@syncfusion/ej2-inputs | AI (dependencies): Same-org sibling package; version-pinned to matching release band. | ai | |
| dependencies | unvetted-dep:@syncfusion/ej2-popups | AI (dependencies): Same-org sibling package; version-pinned to matching release band. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 33.2.7 | 10 / 0 | |
| 33.1.49 | 10 / 0 | |
| 33.1.47 | 10 / 0 | |
| 33.1.46 | 10 / 0 | |
| 32.1.19 | 10 / 0 | |
| 31.2.18 | 8 / 0 | |
| 31.2.15 | 8 / 0 | |
| 31.2.12 | 8 / 0 | |
| 31.2.10 | 8 / 0 | |
| 31.2.5 | 8 / 0 |
v32.1.19
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (syncfusion-javascript) than the most recent previously approved version (essentialjs2) on 2025-12-16, but syncfusion-javascript is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v31.2.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v31.2.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v31.2.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v31.2.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v31.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.