@syncfusion/ej2-lists — Greenflagged

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

ej2Syncfusionweb componentsvirtualizationgroup listcheck listlistview with checkboxlistview templatematerial listui listviewremote listviewnested viewdata listinfinite listsortcheckboxtodolist widgetlist componentmobile listlist gestureses6 listdynamic list

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	missing-githead	AI (provenance): Consistent with the publisher change; no other suspicious signals.	ai	2026/05/30
provenance	no-provenance	AI (provenance): Syncfusion does not publish with Sigstore provenance; stable across versions.	ai	2026/05/30
provenance	publisher-changed	AI (provenance): Org-wide transition to syncfusion-javascript account; 230 approved packages under same publisher.	ai	2026/05/26
license	uncommon-license:SEE LICENSE IN license	AI (license): Standard Syncfusion commercial license pattern; stable across all their packages.	ai	2026/05/26
phantom-deps	phantom-dep:@syncfusion/ej2-popups	AI (phantom-deps): Same-org sibling dep; declared in package.json as a runtime dependency, phantom detection is a false positive for this package.	ai	2026/05/14

Versions (showing 10 of 10)

Version	Deps	Published
33.2.3	4 / 0	2026-04-21
33.1.47	4 / 0	2026-04-07
33.1.44	4 / 0	2026-03-16
32.2.7	4 / 0	2026-02-24
32.2.6	4 / 0	2026-02-17
32.2.3	4 / 0	2026-02-05
32.1.24	4 / 0	2026-01-20
32.1.23	4 / 0	2026-01-13
32.1.19	4 / 0	2025-12-16
31.2.12	4 / 0	2025-11-18

v33.1.47

2 findings

HIGH Publisher changed: essentialjs2 → syncfusion-javascript (on 2026-04-07) provenance

This version was published by a different npm account than previous versions on 2026-04-07. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v33.1.44

2 findings

HIGH Publisher changed: essentialjs2 → syncfusion-javascript (on 2026-03-16) provenance

This version was published by a different npm account than previous versions on 2026-03-16. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v32.2.7

2 findings

HIGH Publisher changed: essentialjs2 → syncfusion-javascript (on 2026-02-24) provenance

This version was published by a different npm account than previous versions on 2026-02-24. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v32.2.6

3 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: syncfusion-javascript.

HIGH Publisher changed: essentialjs2 → syncfusion-javascript (on 2026-02-17) provenance

This version was published by a different npm account than previous versions on 2026-02-17. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v32.2.3

2 findings

HIGH Publisher changed: essentialjs2 → syncfusion-javascript (on 2026-02-05) provenance

This version was published by a different npm account than previous versions on 2026-02-05. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v32.1.24

2 findings

HIGH Publisher changed: essentialjs2 → syncfusion-javascript (on 2026-01-20) provenance

This version was published by a different npm account than previous versions on 2026-01-20. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v32.1.23

2 findings

HIGH Publisher changed: essentialjs2 → syncfusion-javascript (on 2026-01-13) provenance

This version was published by a different npm account than previous versions on 2026-01-13. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v32.1.19

2 findings

HIGH Publisher changed: essentialjs2 → syncfusion-javascript (on 2025-12-16) provenance

This version was published by a different npm account than previous versions on 2025-12-16. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v31.2.12

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.