@syncfusion/ej2-splitbuttons
3
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
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
syncfusionorgessentialjs2syncfusion-javascript
Keywords
ej2syncfusionej2-splitbuttonsej2 splitbuttonej2 dropdownbuttonej2 buttongroupej2 progress buttonJavaScriptTypeScriptsplit buttonsplitbuttondropdowndropdown buttondrop-down buttondropdownbuttondropdown popupbutton groupbuttongroupgroup buttonprogressspinnerprogress buttonprogress indicatorspinbuttonspin button
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Syncfusion does not publish with Sigstore provenance; stable pattern across all their packages. | ai | |
| license | uncommon-license:SEE LICENSE IN license | AI (license): Syncfusion's standard commercial license format; consistent across all their packages. | ai |
v33.2.6
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v33.1.49
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.