@syncfusion/ej2-diagrams
Feature-rich diagram control to create diagrams like flow charts, organizational charts, mind maps, and BPMN diagrams. Its rich feature set includes built-in shapes, editing, serializing, exporting, printing, overview, data binding, and automatic layouts.
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@syncfusion/ej2-lists | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic fires on indirect usage patterns common in Syncfusion's monorepo. | ai | |
| phantom-deps | phantom-dep:@syncfusion/ej2-buttons | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic fires on indirect usage patterns common in Syncfusion's monorepo. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 34.1.31 | 7 / 0 | |
| 34.1.30 | 7 / 0 | |
| 34.1.29 | 7 / 0 | |
| 33.2.15 | 7 / 0 | |
| 33.2.13 | 7 / 0 | |
| 33.2.12 | 7 / 0 | |
| 33.2.10 | 7 / 0 | |
| 33.2.8 | 7 / 0 | |
| 33.2.7 | 7 / 0 | |
| 33.2.6 | 7 / 0 | |
| 33.2.4 | 7 / 0 | |
| 32.1.25 | 7 / 0 | |
| 32.1.24 | 7 / 0 | |
| 32.1.23 | 7 / 0 | |
| 32.1.22 | 7 / 0 | |
| 32.1.21 | 7 / 0 | |
| 32.1.20 | 7 / 0 | |
| 32.1.19 | 7 / 0 | |
| 31.2.18 | 7 / 0 | |
| 31.2.16 | 7 / 0 | |
| 31.2.15 | 7 / 0 | |
| 31.2.12 | 7 / 0 | |
| 31.2.10 | 7 / 0 | |
| 31.2.5 | 7 / 0 |
v34.1.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v34.1.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v34.1.29
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. Consider requesting the maintainer enable provenance via CI/CD.
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
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-23, 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.
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.