@syncfusion/ej2-angular-calendars SEE LICENSE IN license 28 versions

@syncfusion/ej2-angular-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. for Angular

28

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

angularngng-calendarsej2-ng-calendars

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	missing-githead	AI (provenance): Syncfusion's publish pipeline change affects the whole org; no malicious signal, just missing metadata.	ai	2026/05/26
provenance	publisher-changed	AI (provenance): Syncfusion org account migration; syncfusion-javascript has 178 approved packages across the same scope.	ai	2026/05/21
bogus-package	bogus-package	AI (bogus-package): Syncfusion packages consistently have link-heavy READMEs; not a spam/phishing indicator for this org.	ai	2026/05/14
phantom-deps	phantom-dep:@syncfusion/ej2-base	AI (phantom-deps): Same-org transitive dep; phantom-dep heuristic is a stable false positive for this package.	ai	2026/05/14

Versions (showing 28 of 28)

Version	Deps	Published
33.2.10	3 / 0	2026-06-02
33.2.8	3 / 0	2026-05-26
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.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.6	3 / 0	2026-02-24
32.2.5	3 / 0	2026-02-17
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.22	3 / 0	2026-01-06
32.1.21	3 / 0	2025-12-30
32.1.20	3 / 0	2025-12-23
32.1.19	3 / 0	2025-12-16
31.2.18	3 / 0	2025-12-09
31.2.16	3 / 0	2025-12-02
31.2.15	3 / 0	2025-11-25
31.2.12	3 / 0	2025-11-18
31.2.10	3 / 0	2025-11-12
31.2.5	3 / 0	2025-11-04

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

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.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. Only ~12% of npm packages have provenance, so this is common but not ideal.

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. Only ~12% of npm packages have provenance, so this is common but not ideal.

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. Only ~12% of npm packages have provenance, so this is common but not ideal.

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. Only ~12% of npm packages have provenance, so this is common but not ideal.

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

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