@syncfusion/ej2-react-blockeditor
Feature Rich Block Editor control with built in support editing, formatting content. for React
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@syncfusion/ej2-base | AI (phantom-deps): Same-org dependency; stable false positive for Syncfusion React wrapper packages. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Syncfusion packages consistently have link-heavy READMEs; not indicative of spam or phishing. | ai |
Versions (showing 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 33.2.10 | 3 / 0 | |
| 33.2.8 | 3 / 0 | |
| 33.2.7 | 3 / 0 | |
| 33.2.6 | 3 / 0 | |
| 33.2.5 | 3 / 0 | |
| 33.2.4 | 3 / 0 | |
| 33.2.3 | 3 / 0 | |
| 33.1.44 | 3 / 0 | |
| 32.2.9 | 3 / 0 | |
| 32.2.8 | 3 / 0 | |
| 32.2.7 | 3 / 0 | |
| 32.2.5 | 3 / 0 | |
| 32.2.4 | 3 / 0 | |
| 32.2.3 | 3 / 0 | |
| 32.1.25 | 3 / 0 | |
| 32.1.24 | 3 / 0 | |
| 32.1.23 | 3 / 0 | |
| 32.1.22 | 3 / 0 | |
| 32.1.21 | 3 / 0 | |
| 32.1.20 | 3 / 0 | |
| 32.1.19 | 3 / 0 | |
| 31.2.18 | 3 / 0 | |
| 31.2.16 | 3 / 0 | |
| 31.2.15 | 3 / 0 | |
| 31.2.12 | 3 / 0 | |
| 31.2.10 | 3 / 0 | |
| 31.2.5 | 3 / 0 |
v33.2.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v33.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v33.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v33.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v33.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v33.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v33.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v33.1.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v32.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.1.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v32.1.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.1.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.1.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.1.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.1.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v32.1.19
2 findingsPackage 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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v31.2.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v31.2.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v31.2.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v31.2.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v31.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.