@syncfusion/ej2-gantt SEE LICENSE IN license 26 versions

@syncfusion/ej2-gantt

npm Repository Homepage

Essential JS 2 Gantt Component

26

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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

syncfusionorgessentialjs2syncfusion-javascript

Keywords

ej2syncfusionJavaScriptTypeScriptganttgantt-chartproject-managementproject-planningtask-schedulingtimeline-chartproject-trackingproject-timelineresource-managementtask-managementschedule-managementtimeline-managementgantt-viewgantt-chart-componentgantt-chart-control

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 component bundles.	ai	2026/05/26
phantom-deps	phantom-dep:@syncfusion/ej2-notifications	AI (phantom-deps): Same-org sibling dep; same rationale as ej2-lists phantom-dep false positive.	ai	2026/05/26
bogus-package	bogus-package	AI (bogus-package): Syncfusion component READMEs consistently contain many URLs and promotional content; not indicative of spam or phishing.	ai	2026/05/26

Versions (showing 26 of 26)

Version	Deps	Published
34.1.32	15 / 0	2026-07-21
34.1.30	15 / 0	2026-07-09
34.1.29	15 / 0	2026-07-06
33.2.12	15 / 0	2026-06-09
33.2.6	15 / 0	2026-05-12
33.2.3	15 / 0	2026-04-21
33.1.47	15 / 0	2026-04-07
33.1.45	15 / 0	2026-03-24
33.1.44	15 / 0	2026-03-16
32.2.9	15 / 0	2026-03-10
32.2.8	15 / 0	2026-03-03
32.2.7	15 / 0	2026-02-24
32.2.5	15 / 0	2026-02-17
32.2.4	15 / 0	2026-02-11
32.2.3	15 / 0	2026-02-05
32.1.25	15 / 0	2026-01-27
32.1.24	15 / 0	2026-01-20
32.1.23	15 / 0	2026-01-13
32.1.21	15 / 0	2025-12-30
32.1.20	15 / 0	2025-12-23
32.1.19	15 / 0	2025-12-16
31.2.18	15 / 0	2025-12-09
31.2.15	15 / 0	2025-11-25
31.2.12	15 / 0	2025-11-18
31.2.10	15 / 0	2025-11-12
31.2.5	15 / 0	2025-11-04

v34.1.32

1 finding

LOW No provenance attestation provenance

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

v34.1.30

1 finding

LOW No provenance attestation provenance

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

v34.1.29

1 finding

LOW No provenance attestation provenance

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

v33.1.45

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. Consider requesting the maintainer enable provenance via CI/CD.

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

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. Consider requesting the maintainer enable provenance via CI/CD.

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. Consider requesting the maintainer enable provenance via CI/CD.

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

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

LOW No provenance attestation provenance

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

INFO Publisher changed: essentialjs2 → syncfusion-javascript (on 2025-12-16, known maintainer) provenance

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 finding

LOW No provenance attestation provenance

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

v31.2.15

1 finding

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. Consider requesting the maintainer enable provenance via CI/CD.

v31.2.10

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

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.