VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

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

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

Vulert verdict on @syncfusion/ej2-layouts 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 50 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-layouts, 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.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.3 21 Apr 2026 none non-standard — Details →
33.1.47 07 Apr 2026 none non-standard — Details →
33.1.44 16 Mar 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.19 16 Dec 2025 none non-standard — Details →
31.2.12 18 Nov 2025 none non-standard — Details →
31.2.2 15 Oct 2025 none non-standard — Details →
31.1.22 01 Oct 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.40 15 Jul 2025 none non-standard — Details →
30.1.37 25 Jun 2025 none non-standard — Details →
29.2.4 14 May 2025 none non-standard — Details →
29.1.39 22 Apr 2025 none non-standard — Details →
29.1.38 14 Apr 2025 none non-standard — Details →
29.1.37 08 Apr 2025 none non-standard — Details →
29.1.35 01 Apr 2025 none non-standard — Details →
29.1.34 26 Mar 2025 none non-standard — Details →
29.1.33 25 Mar 2025 none non-standard — Details →
28.2.5 11 Feb 2025 none non-standard — Details →
28.2.4 04 Feb 2025 none non-standard — Details →
28.2.3 29 Jan 2025 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 →
27.1.56 23 Oct 2024 none non-standard — Details →
27.1.53 15 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.10 19 Aug 2024 none non-standard — Details →
26.2.9 12 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.38 19 Jun 2024 none non-standard — Details →
26.1.35 11 Jun 2024 none non-standard — Details →
25.2.3 08 May 2024 none non-standard — Details →
25.1.35-579988 24 Apr 2024 none non-standard — Details →
25.1.37 26 Mar 2024 none non-standard — Details →
25.1.35 15 Mar 2024 none non-standard — Details →
24.2.4 06 Feb 2024 none non-standard — Details →
24.2.3 31 Jan 2024 none non-standard — Details →
24.1.41 18 Dec 2023 none non-standard — Details →
23.2.4 20 Nov 2023 none non-standard — Details →
23.1.36 15 Sep 2023 none non-standard — Details →
22.2.9 15 Aug 2023 none non-standard — Details →
22.2.5 27 Jul 2023 none non-standard — Details →
22.1.37 04 Jul 2023 none non-standard — Details →
22.1.36 28 Jun 2023 none non-standard — Details →
21.1.42 28 Jun 2023 none non-standard — Details →
21.1.36 28 Jun 2023 none non-standard — Details →
22.1.34 21 Jun 2023 none non-standard — Details →
21.2.9 06 Jun 2023 none non-standard — Details →
21.2.6 23 May 2023 none non-standard — Details →
21.2.3 03 May 2023 none non-standard — Details →
21.1.37 29 Mar 2023 none non-standard — Details →
21.1.35 23 Mar 2023 none non-standard — Details →
20.4.53 07 Mar 2023 none non-standard — Details →
20.4.48 01 Feb 2023 none non-standard — Details →
20.4.42 04 Jan 2023 none non-standard — Details →
20.4.40 28 Dec 2022 none non-standard — Details →
20.4.38 21 Dec 2022 none non-standard — Details →
20.3.58 22 Nov 2022 none non-standard — Details →
20.3.57 15 Nov 2022 none non-standard — Details →
20.3.56 08 Nov 2022 none non-standard — Details →
20.3.48 05 Oct 2022 none non-standard — Details →
20.3.47 29 Sep 2022 none non-standard — Details →
20.2.46 30 Aug 2022 none non-standard — Details →
20.2.45 23 Aug 2022 none non-standard — Details →
20.2.43 08 Aug 2022 none non-standard — Details →
20.2.39 19 Jul 2022 none non-standard — Details →
20.2.38 12 Jul 2022 none non-standard — Details →
20.2.36 30 Jun 2022 none non-standard — Details →
20.1.61 21 Jun 2022 none non-standard — Details →
20.1.58 31 May 2022 none non-standard — Details →
20.1.55 12 May 2022 none non-standard — Details →
20.1.47 04 Apr 2022 none non-standard — Details →
19.4.52 15 Feb 2022 none non-standard — Details →
19.4.48 31 Jan 2022 none non-standard — Details →
19.4.47 25 Jan 2022 none non-standard — Details →
19.4.43 18 Jan 2022 none non-standard — Details →
19.4.38 17 Dec 2021 none non-standard — Details →
19.3.53 12 Nov 2021 none non-standard — Details →
19.3.48 02 Nov 2021 none non-standard — Details →
19.3.44 05 Oct 2021 none non-standard — Details →
19.3.43 30 Sep 2021 none non-standard — Details →
19.2.60 07 Sep 2021 none non-standard — Details →
19.2.55 11 Aug 2021 none non-standard — Details →
19.2.48 20 Jul 2021 none non-standard — Details →
19.2.44 30 Jun 2021 none non-standard — Details →
19.1.63 13 May 2021 none — — Details →
19.1.58 27 Apr 2021 none — — Details →
19.1.56 13 Apr 2021 none — — Details →
19.1.55 06 Apr 2021 none — — Details →
19.1.54 30 Mar 2021 none — — Details →
18.4.49 23 Mar 2021 none — — Details →
18.4.47 09 Mar 2021 none — — Details →
18.4.44 23 Feb 2021 none — — Details →
18.4.39 28 Jan 2021 none — — Details →
17.2.55-1205479 15 Jan 2021 none — — Details →
18.4.30 17 Dec 2020 none — — Details →
18.3.53 08 Dec 2020 none — — Details →
17.2.52-1205479 23 Nov 2020 none — — Details →
18.3.48 11 Nov 2020 none — — Details →
18.3.47 05 Nov 2020 none — — Details →
18.3.44 27 Oct 2020 none — — Details →
17.2.49-beta 23 Oct 2020 none — — Details →
18.3.40 13 Oct 2020 none — — Details →
18.3.35 01 Oct 2020 none — — Details →
18.2.58 15 Sep 2020 none — — Details →

The newest 120 of 188 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-layouts

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

Is @syncfusion/ej2-layouts safe to use?

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

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

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

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

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