@syncfusion/ej2-calendars SEE LICENSE IN license 32 versions

@syncfusion/ej2-calendars

npm Repository Homepage

A complete package of date or time components with built-in features such as date formatting, inline editing, multiple (range) selection, range restriction, month and year selection, strict mode, and globalization.

32

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

ej2syncfusionej2-calendarsweb-componentsJavaScriptTypeScriptcalendardateculturemonthyeardecadetimepickersteprangestime

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	missing-githead	AI (provenance): Publish-env change on a trusted high-volume Syncfusion package; no code-level risk.	ai	2026/07/14
bogus-package	bogus-package	AI (bogus-package): README link-dump is normal for this commercial UI-controls docs; not spam.	ai	2026/07/14

Versions (showing 32 of 32)

Version	Deps	Published
34.1.29	5 / 0	2026-07-06
33.2.15	5 / 0	2026-06-23
33.2.13	5 / 0	2026-06-16
33.2.12	5 / 0	2026-06-09
33.2.10	5 / 0	2026-06-02
33.2.8	5 / 0	2026-05-26
33.2.7	5 / 0	2026-05-19
33.2.6	5 / 0	2026-05-12
33.2.5	5 / 0	2026-05-05
33.2.4	5 / 0	2026-04-28
33.2.3	5 / 0	2026-04-21
33.1.44	5 / 0	2026-03-16
32.2.9	5 / 0	2026-03-10
32.2.8	5 / 0	2026-03-03
32.2.7	5 / 0	2026-02-24
32.2.6	5 / 0	2026-02-17
32.2.5	5 / 0	2026-02-17
32.2.4	5 / 0	2026-02-11
32.2.3	5 / 0	2026-02-05
32.1.25	5 / 0	2026-01-27
32.1.24	5 / 0	2026-01-20
32.1.23	5 / 0	2026-01-13
32.1.22	5 / 0	2026-01-06
32.1.21	5 / 0	2025-12-30
32.1.20	5 / 0	2025-12-23
32.1.19	5 / 0	2025-12-16
31.2.18	5 / 0	2025-12-09
31.2.16	5 / 0	2025-12-02
31.2.15	5 / 0	2025-11-25
31.2.12	5 / 0	2025-11-18
31.2.10	5 / 0	2025-11-12
31.2.5	5 / 0	2025-11-04

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

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

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

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

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.