VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

@syncfusion/ej2-calendars: vulnerability history, versions and safety

@syncfusion/ej2-calendars is a package in the npm ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the npm ecosystem.

i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all @syncfusion/ej2-calendars vulnerabilities

Vulert verdict on @syncfusion/ej2-calendars 35.1.41 i

Updated on 23 Oct 2026

Good news: 35.1.41, the version you would install today, has no known vulnerabilities.

Package health score 74/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Quiet

What to do: Stay on 35.1.41 or newer. This can change: a vulnerability disclosed tomorrow can affect 35.1.41 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 35.1.41 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 82 packages i
  • Stars 449 i
  • OpenSSF scorecard 2/10 i
  • Last release this month i
  • Licence non-standard i

Version list, release dates, licence and dependants published by the npm registry, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for @syncfusion/ej2-calendars, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
35.1.41 20 Oct 2026 none non-standard — Details →
35.1.39 07 Oct 2026 none non-standard — Details →
35.1.37 29 Sep 2026 none non-standard — Details →
34.2.8 15 Sep 2026 none non-standard — Details →
34.2.6 01 Sep 2026 none non-standard — Details →
34.2.5 25 Aug 2026 none non-standard — Details →
34.2.4 18 Aug 2026 none non-standard — Details →
34.2.3 11 Aug 2026 none non-standard — Details →
34.2.2 05 Aug 2026 none non-standard — Details →
34.1.29 06 Jul 2026 none non-standard — Details →
33.2.15 23 Jun 2026 none non-standard — Details →
33.2.13 16 Jun 2026 none non-standard — Details →
33.2.12 09 Jun 2026 none non-standard — Details →
33.2.10 02 Jun 2026 none non-standard — Details →
33.2.8 26 May 2026 none non-standard — Details →
33.2.7 19 May 2026 none non-standard — Details →
33.2.6 12 May 2026 none non-standard — Details →
33.2.5 05 May 2026 none non-standard — Details →
33.2.4 28 Apr 2026 none non-standard — Details →
33.2.3 21 Apr 2026 none non-standard — Details →
33.1.44 16 Mar 2026 none non-standard — Details →
32.2.9 10 Mar 2026 none non-standard — Details →
32.2.8 03 Mar 2026 none non-standard — Details →
32.2.7 24 Feb 2026 none non-standard — Details →
32.2.6 17 Feb 2026 none non-standard — Details →
32.2.5 17 Feb 2026 none non-standard — Details →
32.2.4 11 Feb 2026 none non-standard — Details →
32.2.3 05 Feb 2026 none non-standard — Details →
32.1.25 27 Jan 2026 none non-standard — Details →
32.1.24 20 Jan 2026 none non-standard — Details →
32.1.23 13 Jan 2026 none non-standard — Details →
32.1.22 06 Jan 2026 none non-standard — Details →
32.1.21 30 Dec 2025 none non-standard — Details →
32.1.20 23 Dec 2025 none non-standard — Details →
32.1.19 16 Dec 2025 none non-standard — Details →
31.2.18 09 Dec 2025 none non-standard — Details →
31.2.16 02 Dec 2025 none non-standard — Details →
31.2.15 25 Nov 2025 none non-standard — Details →
31.2.12 18 Nov 2025 none non-standard — Details →
31.2.10 12 Nov 2025 none non-standard — Details →
31.2.5 04 Nov 2025 none non-standard — Details →
31.2.4 28 Oct 2025 none non-standard — Details →
31.2.3 22 Oct 2025 none non-standard — Details →
31.2.2 15 Oct 2025 none non-standard — Details →
26.1.35-7502 07 Oct 2025 none non-standard — Details →
31.1.23 07 Oct 2025 none non-standard — Details →
31.1.22 01 Oct 2025 none non-standard — Details →
26.1.35-750253 26 Sep 2025 none non-standard — Details →
31.1.21 23 Sep 2025 none non-standard — Details →
31.1.20 17 Sep 2025 none non-standard — Details →
31.1.19 11 Sep 2025 none non-standard — Details →
31.1.18 10 Sep 2025 none non-standard — Details →
31.1.17 05 Sep 2025 none non-standard — Details →
30.2.4 07 Aug 2025 none non-standard — Details →
30.1.37 25 Jun 2025 none non-standard — Details →
29.2.11 17 Jun 2025 none non-standard — Details →
29.2.10 10 Jun 2025 none non-standard — Details →
29.2.5 21 May 2025 none non-standard — Details →
29.2.4 14 May 2025 none non-standard — Details →
29.1.40 29 Apr 2025 none non-standard — Details →
29.1.39 22 Apr 2025 none non-standard — Details →
29.1.35 01 Apr 2025 none non-standard — Details →
29.1.33 25 Mar 2025 none non-standard — Details →
28.2.11 11 Mar 2025 none non-standard — Details →
28.2.9 04 Mar 2025 none non-standard — Details →
28.2.7 25 Feb 2025 none non-standard — Details →
28.2.3 29 Jan 2025 none non-standard — Details →
28.1.41 21 Jan 2025 none non-standard — Details →
28.1.39 14 Jan 2025 none non-standard — Details →
28.1.37 30 Dec 2024 none non-standard — Details →
28.1.36 24 Dec 2024 none non-standard — Details →
28.1.35 18 Dec 2024 none non-standard — Details →
28.1.33 12 Dec 2024 none non-standard — Details →
27.2.3 21 Nov 2024 none non-standard — Details →
27.2.2 15 Nov 2024 none non-standard — Details →
21.2.10-11964 12 Nov 2024 none non-standard — Details →
27.1.57 28 Oct 2024 none non-standard — Details →
25.2.7-30676 24 Oct 2024 none non-standard — Details →
27.1.55 22 Oct 2024 none non-standard — Details →
27.1.52 08 Oct 2024 none non-standard — Details →
27.1.51 30 Sep 2024 none non-standard — Details →
27.1.50 23 Sep 2024 none non-standard — Details →
27.1.48 18 Sep 2024 none non-standard — Details →
26.2.12 02 Sep 2024 none non-standard — Details →
26.2.11 26 Aug 2024 none non-standard — Details →
26.2.10 19 Aug 2024 none non-standard — Details →
26.2.8 05 Aug 2024 none non-standard — Details →
26.2.5 25 Jul 2024 none non-standard — Details →
26.2.4 24 Jul 2024 none non-standard — Details →
26.1.41 09 Jul 2024 none non-standard — Details →
26.1.40 02 Jul 2024 none non-standard — Details →
26.1.38 19 Jun 2024 none non-standard — Details →
26.1.35 11 Jun 2024 none non-standard — Details →
25.2.7 04 Jun 2024 none non-standard — Details →
25.2.5 21 May 2024 none non-standard — Details →
25.2.4 14 May 2024 none non-standard — Details →
25.2.3 08 May 2024 none non-standard — Details →
25.1.42 30 Apr 2024 none non-standard — Details →
25.1.40 16 Apr 2024 none non-standard — Details →
25.1.39 09 Apr 2024 none non-standard — Details →
25.1.37 26 Mar 2024 none — — Details →
25.1.35 15 Mar 2024 none — — Details →
24.2.9 05 Mar 2024 none — — Details →
24.2.8 27 Feb 2024 none — — Details →
24.2.5 13 Feb 2024 none — — Details →
24.2.3 31 Jan 2024 none — — Details →
24.1.47 23 Jan 2024 none — — Details →
24.1.44 03 Jan 2024 none — — Details →
24.1.43 27 Dec 2023 none — — Details →
24.1.41 18 Dec 2023 none — — Details →
23.2.7 05 Dec 2023 none — — Details →
23.2.6 28 Nov 2023 none — — Details →
23.2.4 20 Nov 2023 none — — Details →
23.1.41 17 Oct 2023 none — — Details →
23.1.40 10 Oct 2023 none — — Details →
23.1.38 26 Sep 2023 none — — Details →
23.1.36 15 Sep 2023 none — — Details →
22.2.12 05 Sep 2023 none — — Details →
22.2.11 29 Aug 2023 none — — Details →
22.2.10 22 Aug 2023 none — — Details →

The newest 120 of 324 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

No dated vulnerabilities are recorded for this package yet.

03 Vulnerabilities

Recorded vulnerabilities for @syncfusion/ej2-calendars

No vulnerability write-ups match this view

Search all 0 in the database →

No vulnerabilities match this view.

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About @syncfusion/ej2-calendars

Is @syncfusion/ej2-calendars safe to use?

Vulert has no vulnerabilities on record for @syncfusion/ej2-calendars in npm at this point. That is a good signal rather than a guarantee: new vulnerabilities are published for packages all the time, so the versions you actually run are still worth monitoring.

What is @syncfusion/ej2-calendars's Vulert package health score?

Vulert scores @syncfusion/ej2-calendars 74/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of @syncfusion/ej2-calendars affected?

No. 35.1.41, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

How many vulnerabilities does @syncfusion/ej2-calendars have?

0 vulnerabilities are recorded for @syncfusion/ej2-calendars in the npm ecosystem: 0 critical, 0 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new @syncfusion/ej2-calendars vulnerabilities disclosed?

0 vulnerabilities were recorded for @syncfusion/ej2-calendars in the last 12 months. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of @syncfusion/ej2-calendars are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor @syncfusion/ej2-calendars for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the @syncfusion/ej2-calendars version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.