VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

@podium/layout: vulnerability history, versions and safety

@podium/layout is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 12 releases, first recorded in Apr 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded H1
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 @podium/layout vulnerabilities

Vulert verdict on @podium/layout 5.4.10 i

Updated on 23 Oct 2026

Good news: 5.4.10, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 1.

Package health score 60/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Inactive

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

  • Current release 5.4.10 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 07 Apr 2022 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Stars 1 i
  • OpenSSF scorecard 1/10 i
  • Last release this month i
  • Licence MIT 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 @podium/layout, 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
5.4.10 19 Oct 2026 none MIT — Details →
5.4.9 28 Sep 2026 none MIT — Details →
5.4.8 07 Sep 2026 none MIT — Details →
5.4.7 27 Jul 2026 none MIT — Details →
5.4.6 06 Jul 2026 none MIT — Details →
5.4.5 25 Jun 2026 none MIT — Details →
5.4.4 22 Jun 2026 none MIT — Details →
5.4.3 08 Jun 2026 none MIT — Details →
5.4.2 27 Apr 2026 none MIT — Details →
5.4.1 20 Apr 2026 none MIT — Details →
5.4.0 07 Apr 2026 none MIT — Details →
5.3.10 16 Mar 2026 none MIT — Details →
5.3.9 16 Feb 2026 none MIT — Details →
5.3.8 12 Jan 2026 none MIT — Details →
5.3.7 15 Dec 2025 none MIT — Details →
5.3.6 12 Dec 2025 none MIT — Details →
5.3.5 15 Sep 2025 none MIT — Details →
5.3.4 25 Aug 2025 none MIT — Details →
5.3.3 11 Aug 2025 none MIT — Details →
5.3.2 07 Jul 2025 none MIT — Details →
5.3.1 30 Jun 2025 none MIT — Details →
5.3.0 24 Jun 2025 none MIT — Details →
5.2.20 23 May 2025 none MIT — Details →
5.2.19 20 Jan 2025 none MIT — Details →
5.2.19-beta.3 13 Jan 2025 none MIT — Details →
5.2.19-beta.2 13 Jan 2025 none MIT — Details →
5.2.19-beta.1 03 Dec 2024 none MIT — Details →
5.2.18 02 Dec 2024 none MIT — Details →
5.2.17 25 Nov 2024 none MIT — Details →
5.2.16 18 Nov 2024 none MIT — Details →
5.2.15 13 Nov 2024 none MIT — Details →
5.2.14 06 Nov 2024 none MIT — Details →
5.2.14-next.1 06 Nov 2024 none MIT — Details →
5.2.13-next.3 06 Nov 2024 none MIT — Details →
5.2.13-next.2 04 Nov 2024 none MIT — Details →
5.2.13 04 Nov 2024 none MIT — Details →
5.2.13-next.1 22 Oct 2024 none MIT — Details →
5.2.12 18 Oct 2024 none MIT — Details →
5.2.12-next.1 15 Oct 2024 none MIT — Details →
5.2.11 14 Oct 2024 none MIT — Details →
5.2.10 07 Oct 2024 none MIT — Details →
5.2.9 24 Sep 2024 none MIT — Details →
5.2.8 23 Sep 2024 none MIT — Details →
5.2.7 23 Sep 2024 none MIT — Details →
5.2.7-next.1 16 Sep 2024 none MIT — Details →
5.2.6-next.2 16 Sep 2024 none MIT — Details →
5.2.6 16 Sep 2024 none MIT — Details →
5.2.6-next.1 13 Sep 2024 none MIT — Details →
5.2.5 09 Sep 2024 none MIT — Details →
5.2.4 26 Aug 2024 none MIT — Details →
5.2.3 25 Aug 2024 none MIT — Details →
5.2.2 19 Aug 2024 none MIT — Details →
5.2.1 12 Aug 2024 none MIT — Details →
5.2.0 12 Aug 2024 none MIT — Details →
5.1.20 12 Aug 2024 none MIT — Details →
5.1.19 05 Aug 2024 none MIT — Details →
5.1.18 25 Jul 2024 none MIT — Details →
5.1.17 15 Jul 2024 none MIT — Details →
5.1.16 08 Jul 2024 none MIT — Details →
5.1.15 01 Jul 2024 none MIT — Details →
5.1.14 24 Jun 2024 none MIT — Details →
5.1.13 17 Jun 2024 none MIT — Details →
5.1.12 10 Jun 2024 none MIT — Details →
5.1.11 03 Jun 2024 none MIT — Details →
5.1.10 27 May 2024 none MIT — Details →
5.1.9 23 May 2024 none MIT — Details →
5.1.8 16 May 2024 none MIT — Details →
5.1.7 15 May 2024 none MIT — Details →
5.1.6 14 May 2024 none MIT — Details →
5.1.5 14 May 2024 none MIT — Details →
5.1.4 15 Apr 2024 none MIT — Details →
5.1.3 11 Apr 2024 none MIT — Details →
5.2.0-beta.1 20 Mar 2024 none MIT — Details →
5.1.2 04 Mar 2024 none MIT — Details →
5.1.1 14 Feb 2024 none MIT — Details →
5.1.0 13 Feb 2024 none MIT — Details →
5.0.11 05 Feb 2024 none MIT — Details →
5.0.10 29 Jan 2024 none MIT — Details →
5.0.9 08 Jan 2024 none MIT — Details →
5.0.8 18 Dec 2023 none MIT — Details →
5.0.7 11 Dec 2023 none MIT — Details →
5.0.6 11 Dec 2023 none MIT — Details →
5.0.5 07 Dec 2023 none MIT — Details →
5.0.4 06 Dec 2023 none MIT — Details →
5.0.3 03 Dec 2023 none MIT — Details →
5.0.2 01 Dec 2023 none MIT — Details →
5.0.1 29 Nov 2023 none MIT — Details →
5.0.0 29 Nov 2023 none MIT — Details →
5.0.0-next.10 29 Nov 2023 none MIT — Details →
4.6.125 23 Oct 2023 none MIT — Details →
4.6.124 16 Oct 2023 none MIT — Details →
4.6.123 09 Oct 2023 none MIT — Details →
4.6.122 25 Sep 2023 none MIT — Details →
4.6.121 18 Sep 2023 none MIT — Details →
4.6.120 12 May 2023 none MIT — Details →
4.6.119 27 Mar 2023 none MIT — Details →
4.6.118 20 Feb 2023 none MIT — Details →
4.6.117 09 Jan 2023 none MIT — Details →
4.6.116 12 Dec 2022 none MIT — Details →
4.6.115 21 Nov 2022 none MIT — Details →
4.6.114 14 Nov 2022 none — — Details →
4.6.113 18 Oct 2022 none — — Details →
5.0.0-next.9 21 Sep 2022 none — — Details →
5.0.0-next.8 21 Sep 2022 none — — Details →
4.6.112 01 Sep 2022 none — — Details →
5.0.0-next.7 10 May 2022 none — — Details →
4.6.111 09 May 2022 none — — Details →
4.6.110 05 Apr 2022 none — — Details →
4.6.109 28 Mar 2022 H1 — Yes Details →
4.6.108 14 Feb 2022 H1 — Yes Details →
4.6.107 22 Nov 2021 H1 — Yes Details →
4.6.106 17 Nov 2021 H1 — Yes Details →
4.6.105 15 Nov 2021 H1 — Yes Details →
4.6.104 14 Nov 2021 H1 — Yes Details →
4.6.103 14 Nov 2021 H1 — Yes Details →
4.6.102 13 Nov 2021 H1 — Yes Details →
4.6.101 09 Nov 2021 H1 — Yes Details →
4.6.100 27 Oct 2021 H1 — Yes Details →
4.6.99 27 Oct 2021 H1 — Yes Details →
4.6.98 13 Sep 2021 H1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 1 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for @podium/layout

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2022-24822: Denial of Service vulnerability in @podium/layout and @podium/proxy 7.5 high 4.6.110 07 Apr 2022

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 @podium/layout

Is @podium/layout safe to use?

Vulert records 1 vulnerabilities for @podium/layout in npm: 0 critical, 1 high, 0 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is @podium/layout's Vulert package health score?

Vulert scores @podium/layout 60/100, which reads as usable, but worth attention. 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 @podium/layout affected?

No. 5.4.10, 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 @podium/layout have?

1 vulnerability is recorded for @podium/layout in the npm ecosystem: 0 critical, 1 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 @podium/layout vulnerabilities disclosed?

0 vulnerabilities were recorded for @podium/layout in the last 12 months, and the oldest entry in this database dates to 07 Apr 2022. 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 @podium/layout 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 @podium/layout for upcoming vulnerabilities?

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