@syncfusion/ej2-react-querybuilder SEE LICENSE IN license 22 versions

@syncfusion/ej2-react-querybuilder

npm Repository Homepage

Essential JS 2 QueryBuilder for React

22

Versions

SEE LICENSE IN license

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

reactreactjssyncfusion react query builderreact query builderreact query designerreact filter

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): syncfusion-javascript is the established Syncfusion org account with 440 approved packages; transition from essentialjs2 is a known org migration.	ai	2026/05/30
dependencies	unvetted-dep:@syncfusion/ej2-querybuilder	AI (dependencies): Same-org Syncfusion dependency; expected peer for this React wrapper package across all versions.	ai	2026/05/26
phantom-deps	phantom-dep:@syncfusion/ej2-base	AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic false positive for this package family.	ai	2026/05/14

Versions (showing 22 of 22)

Version	Deps	Published
33.2.10	3 / 0	2026-06-02
33.2.7	3 / 0	2026-05-19
33.2.6	3 / 0	2026-05-12
33.2.5	3 / 0	2026-05-05
33.2.4	3 / 0	2026-04-28
33.2.3	3 / 0	2026-04-21
33.1.49	3 / 0	2026-04-14
33.1.46	3 / 0	2026-03-31
33.1.44	3 / 0	2026-03-16
32.2.9	3 / 0	2026-03-10
32.2.8	3 / 0	2026-03-03
32.2.7	3 / 0	2026-02-24
32.2.4	3 / 0	2026-02-11
32.2.3	3 / 0	2026-02-05
32.1.25	3 / 0	2026-01-27
32.1.24	3 / 0	2026-01-20
32.1.23	3 / 0	2026-01-13
32.1.21	3 / 0	2025-12-30
32.1.19	3 / 0	2025-12-16
31.2.16	3 / 0	2025-12-02
31.2.15	3 / 0	2025-11-25
31.2.12	3 / 0	2025-11-18

v33.2.10

1 finding

LOW No provenance attestation provenance

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

v33.2.7

1 finding

LOW No provenance attestation provenance

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

v33.2.6

1 finding

LOW No provenance attestation provenance

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

v33.2.5

1 finding

LOW No provenance attestation provenance

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

v33.2.3

1 finding

LOW No provenance attestation provenance

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

v33.1.49

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.

v33.1.46

1 finding

LOW No provenance attestation provenance

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

v33.1.44

1 finding

LOW No provenance attestation provenance

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

v32.2.9

1 finding

LOW No provenance attestation provenance

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

v32.2.8

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.

v32.2.7

1 finding

LOW No provenance attestation provenance

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

v32.2.4

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.

v32.2.3

1 finding

LOW No provenance attestation provenance

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

v32.1.25

1 finding

LOW No provenance attestation provenance

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

v32.1.24

1 finding

LOW No provenance attestation provenance

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

v32.1.23

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.

v32.1.21

1 finding

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.16

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.

v31.2.15

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.

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.