VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

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

@syncfusion/ej2-angular-charts 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-angular-charts vulnerabilities

Vulert verdict on @syncfusion/ej2-angular-charts 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 72/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 1 packages i
  • Stars 294 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-angular-charts, 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.8-ngcc 15 Sep 2026 none non-standard — Details →
34.2.6 01 Sep 2026 none non-standard — Details →
34.2.6-ngcc 01 Sep 2026 none non-standard — Details →
34.2.5 25 Aug 2026 none non-standard — Details →
34.2.5-ngcc 25 Aug 2026 none non-standard — Details →
34.2.4 18 Aug 2026 none non-standard — Details →
34.2.4-ngcc 18 Aug 2026 none non-standard — Details →
34.2.3 11 Aug 2026 none non-standard — Details →
34.2.3-ngcc 11 Aug 2026 none non-standard — Details →
34.2.2 05 Aug 2026 none non-standard — Details →
34.2.2-ngcc 05 Aug 2026 none non-standard — Details →
34.1.33 28 Jul 2026 none non-standard — Details →
34.1.33-ngcc 28 Jul 2026 none non-standard — Details →
34.1.29 06 Jul 2026 none non-standard — Details →
34.1.29-ngcc 06 Jul 2026 none non-standard — Details →
33.2.15 23 Jun 2026 none non-standard — Details →
33.2.15-ngcc 23 Jun 2026 none non-standard — Details →
29.2.4-849217 18 Jun 2026 none non-standard — Details →
29.2.4-846791 16 Jun 2026 none non-standard — Details →
33.2.13 16 Jun 2026 none non-standard — Details →
33.2.13-ngcc 16 Jun 2026 none non-standard — Details →
33.2.12 09 Jun 2026 none non-standard — Details →
33.2.12-ngcc 09 Jun 2026 none non-standard — Details →
33.2.10 02 Jun 2026 none non-standard — Details →
33.2.10-ngcc 02 Jun 2026 none non-standard — Details →
33.2.8 26 May 2026 none non-standard — Details →
33.2.8-ngcc 26 May 2026 none non-standard — Details →
33.2.6 12 May 2026 none non-standard — Details →
33.2.6-ngcc 12 May 2026 none non-standard — Details →
33.2.5 05 May 2026 none non-standard — Details →
33.2.5-ngcc 05 May 2026 none non-standard — Details →
33.2.4 28 Apr 2026 none non-standard — Details →
33.2.4-ngcc 28 Apr 2026 none non-standard — Details →
33.2.3 21 Apr 2026 none non-standard — Details →
33.2.3-ngcc 21 Apr 2026 none non-standard — Details →
33.1.49 14 Apr 2026 none non-standard — Details →
33.1.49-ngcc 14 Apr 2026 none non-standard — Details →
33.1.47 07 Apr 2026 none non-standard — Details →
33.1.47-ngcc 07 Apr 2026 none non-standard — Details →
33.1.44 16 Mar 2026 none non-standard — Details →
33.1.44-ngcc 16 Mar 2026 none non-standard — Details →
32.2.9 10 Mar 2026 none non-standard — Details →
32.2.9-ngcc 10 Mar 2026 none non-standard — Details →
32.2.8 03 Mar 2026 none non-standard — Details →
32.2.8-ngcc 03 Mar 2026 none non-standard — Details →
32.2.7 24 Feb 2026 none non-standard — Details →
32.2.7-ngcc 24 Feb 2026 none non-standard — Details →
32.2.5 17 Feb 2026 none non-standard — Details →
32.2.5-ngcc 17 Feb 2026 none non-standard — Details →
32.2.4 11 Feb 2026 none non-standard — Details →
32.2.4-ngcc 11 Feb 2026 none non-standard — Details →
32.2.3 05 Feb 2026 none non-standard — Details →
32.2.3-ngcc 05 Feb 2026 none non-standard — Details →
32.1.25 27 Jan 2026 none non-standard — Details →
32.1.25-ngcc 27 Jan 2026 none non-standard — Details →
32.1.24 20 Jan 2026 none non-standard — Details →
32.1.24-ngcc 20 Jan 2026 none non-standard — Details →
32.1.23 13 Jan 2026 none non-standard — Details →
32.1.23-ngcc 13 Jan 2026 none non-standard — Details →
32.1.22 06 Jan 2026 none non-standard — Details →
32.1.22-ngcc 06 Jan 2026 none non-standard — Details →
32.1.19 16 Dec 2025 none non-standard — Details →
32.1.19-ngcc 16 Dec 2025 none non-standard — Details →
31.2.18 09 Dec 2025 none non-standard — Details →
31.2.18-ngcc 09 Dec 2025 none non-standard — Details →
31.2.16 02 Dec 2025 none non-standard — Details →
31.2.16-ngcc 02 Dec 2025 none non-standard — Details →
31.2.15 25 Nov 2025 none non-standard — Details →
31.2.15-ngcc 25 Nov 2025 none non-standard — Details →
31.2.12 18 Nov 2025 none non-standard — Details →
31.2.12-ngcc 18 Nov 2025 none non-standard — Details →
31.2.10 12 Nov 2025 none non-standard — Details →
31.2.10-ngcc 12 Nov 2025 none non-standard — Details →
31.2.5 04 Nov 2025 none non-standard — Details →
31.2.5-ngcc 04 Nov 2025 none non-standard — Details →
31.2.4 28 Oct 2025 none non-standard — Details →
31.2.4-ngcc 28 Oct 2025 none non-standard — Details →
31.2.3 22 Oct 2025 none non-standard — Details →
31.2.3-ngcc 22 Oct 2025 none non-standard — Details →
31.2.2 15 Oct 2025 none non-standard — Details →
31.2.2-ngcc 15 Oct 2025 none non-standard — Details →
31.1.23 07 Oct 2025 none non-standard — Details →
31.1.23-ngcc 07 Oct 2025 none non-standard — Details →
31.1.22 01 Oct 2025 none non-standard — Details →
31.1.22-ngcc 01 Oct 2025 none non-standard — Details →
31.1.21 23 Sep 2025 none non-standard — Details →
31.1.21-ngcc 23 Sep 2025 none non-standard — Details →
31.1.20 17 Sep 2025 none non-standard — Details →
31.1.20-ngcc 17 Sep 2025 none non-standard — Details →
31.1.19 11 Sep 2025 none non-standard — Details →
31.1.19-ngcc 11 Sep 2025 none non-standard — Details →
31.1.18 10 Sep 2025 none non-standard — Details →
31.1.18-ngcc 10 Sep 2025 none non-standard — Details →
31.1.17 05 Sep 2025 none non-standard — Details →
31.1.17-ngcc 05 Sep 2025 none non-standard — Details →
30.2.7 26 Aug 2025 none non-standard — Details →
30.2.7-ngcc 26 Aug 2025 none — — Details →
30.2.6 19 Aug 2025 none — — Details →
30.2.6-ngcc 19 Aug 2025 none — — Details →
30.2.5 13 Aug 2025 none — — Details →
30.2.5-ngcc 13 Aug 2025 none — — Details →
30.2.4 07 Aug 2025 none — — Details →
30.2.4-ngcc 07 Aug 2025 none — — Details →
30.1.42 29 Jul 2025 none — — Details →
30.1.42-ngcc 29 Jul 2025 none — — Details →
30.1.41 22 Jul 2025 none — — Details →
30.1.41-ngcc 22 Jul 2025 none — — Details →
30.1.40 15 Jul 2025 none — — Details →
30.1.40-ngcc 15 Jul 2025 none — — Details →
30.1.39 08 Jul 2025 none — — Details →
30.1.39-ngcc 08 Jul 2025 none — — Details →
30.1.37 25 Jun 2025 none — — Details →
30.1.37-ngcc 25 Jun 2025 none — — Details →
29.2.11 17 Jun 2025 none — — Details →
29.2.11-ngcc 17 Jun 2025 none — — Details →
29.2.10 10 Jun 2025 none — — Details →

The newest 120 of 558 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-angular-charts

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-angular-charts

Is @syncfusion/ej2-angular-charts safe to use?

Vulert has no vulnerabilities on record for @syncfusion/ej2-angular-charts 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-angular-charts's Vulert package health score?

Vulert scores @syncfusion/ej2-angular-charts 72/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-angular-charts 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-angular-charts have?

0 vulnerabilities are recorded for @syncfusion/ej2-angular-charts 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-angular-charts vulnerabilities disclosed?

0 vulnerabilities were recorded for @syncfusion/ej2-angular-charts 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-angular-charts 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-angular-charts for upcoming vulnerabilities?

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