VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

@chakra-ui/layout: vulnerability history, versions and safety

@chakra-ui/layout 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 @chakra-ui/layout vulnerabilities

Vulert verdict on @chakra-ui/layout 2.3.1 i

Updated on 23 Oct 2026

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

Package health score 69/100
  • Security Minor issues
  • Maintenance Slowing
  • Popularity Widely used
  • Community Moderate

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

  • Current release 2.3.1 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 75 packages i
  • Stars 40,698 i
  • OpenSSF scorecard 4/10 i
  • Last release 37 months ago 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 @chakra-ui/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
2.3.1 08 Sep 2023 none MIT — Details →
0.0.0-dev-20230908144305 08 Sep 2023 none MIT — Details →
0.0.0-dev-20230830133821 30 Aug 2023 none MIT — Details →
0.0.0-dev-20230830120642 30 Aug 2023 none MIT — Details →
0.0.0-dev-20230830093747 30 Aug 2023 none MIT — Details →
0.0.0-dev-20230822134434 22 Aug 2023 none MIT — Details →
0.0.0-dev-20230822131635 22 Aug 2023 none MIT — Details →
2.3.0 18 Jul 2023 none MIT — Details →
0.0.0-dev-20230718132637 18 Jul 2023 none MIT — Details →
0.0.0-dev-20230718130742 18 Jul 2023 none MIT — Details →
0.0.0-dev-20230718124717 18 Jul 2023 none MIT — Details →
0.0.0-dev-20230718122336 18 Jul 2023 none MIT — Details →
2.2.0 31 May 2023 none MIT — Details →
0.0.0-dev-20230531085907 31 May 2023 none MIT — Details →
0.0.0-dev-20230531084037 31 May 2023 none MIT — Details →
0.0.0-dev-20230531082239 31 May 2023 none MIT — Details →
0.0.0-dev-20230528200306 28 May 2023 none MIT — Details →
0.0.0-dev-20230528194103 28 May 2023 none MIT — Details →
0.0.0-dev-20230528190715 28 May 2023 none MIT — Details →
0.0.0-dev-20230528185153 28 May 2023 none MIT — Details →
0.0.0-dev-20230528183722 28 May 2023 none MIT — Details →
0.0.0-dev-20230528181900 28 May 2023 none MIT — Details →
2.1.19 25 Apr 2023 none MIT — Details →
0.0.0-dev-20230424225650 24 Apr 2023 none MIT — Details →
0.0.0-dev-20230424222806 24 Apr 2023 none MIT — Details →
0.0.0-dev-20230424221053 24 Apr 2023 none MIT — Details →
0.0.0-dev-20230424210540 24 Apr 2023 none MIT — Details →
0.0.0-dev-20230424205150 24 Apr 2023 none MIT — Details →
0.0.0-dev-20230424202839 24 Apr 2023 none MIT — Details →
0.0.0-dev-20230424201223 24 Apr 2023 none MIT — Details →
2.1.18 30 Mar 2023 none MIT — Details →
0.0.0-dev-20230330130626 30 Mar 2023 none MIT — Details →
0.0.0-dev-20230330124619 30 Mar 2023 none MIT — Details →
0.0.0-dev-20230330123203 30 Mar 2023 none MIT — Details →
0.0.0-dev-20230329144927 29 Mar 2023 none MIT — Details →
0.0.0-dev-20230329141708 29 Mar 2023 none MIT — Details →
0.0.0-dev-20230329140150 29 Mar 2023 none MIT — Details →
0.0.0-dev-20230329123951 29 Mar 2023 none MIT — Details →
2.1.17 23 Mar 2023 none MIT — Details →
0.0.0-dev-20230320184810 20 Mar 2023 none MIT — Details →
0.0.0-dev-20230320183136 20 Mar 2023 none MIT — Details →
2.1.16 13 Feb 2023 none MIT — Details →
0.0.0-dev-20230213131136 13 Feb 2023 none MIT — Details →
0.0.0-dev-20230213124817 13 Feb 2023 none MIT — Details →
0.0.0-dev-20230213123249 13 Feb 2023 none MIT — Details →
0.0.0-dev-20230208114919 08 Feb 2023 none MIT — Details →
0.0.0-dev-20230208112929 08 Feb 2023 none MIT — Details →
0.0.0-dev-20230207153012 07 Feb 2023 none MIT — Details →
2.1.15 16 Jan 2023 none MIT — Details →
0.0.0-dev-20230116124502 16 Jan 2023 none MIT — Details →
0.0.0-dev-20230116122157 16 Jan 2023 none MIT — Details →
0.0.0-dev-20230116120206 16 Jan 2023 none MIT — Details →
2.1.14 12 Jan 2023 none MIT — Details →
0.0.0-dev-20230112154520 12 Jan 2023 none MIT — Details →
0.0.0-dev-20230112152756 12 Jan 2023 none MIT — Details →
0.0.0-dev-20230112145104 12 Jan 2023 none MIT — Details →
0.0.0-dev-20230112143332 12 Jan 2023 none MIT — Details →
0.0.0-dev-20230112141201 12 Jan 2023 none MIT — Details →
0.0.0-dev-20230112113621 12 Jan 2023 none MIT — Details →
0.0.0-dev-20230111211417 11 Jan 2023 none MIT — Details →
2.1.13 11 Jan 2023 none MIT — Details →
0.0.0-dev-20230111055325 11 Jan 2023 none MIT — Details →
0.0.0-dev-20230106083209 06 Jan 2023 none MIT — Details →
0.0.0-dev-20230102095417 02 Jan 2023 none MIT — Details →
0.0.0-dev-20230102093714 02 Jan 2023 none MIT — Details →
2.1.12 26 Dec 2022 none MIT — Details →
0.0.0-dev-20221223180742 23 Dec 2022 none MIT — Details →
0.0.0-dev-20221222051548 22 Dec 2022 none MIT — Details →
0.0.0-dev-20221221152939 21 Dec 2022 none MIT — Details →
0.0.0-dev-20221221133224 21 Dec 2022 none MIT — Details →
0.0.0-dev-20221221110721 21 Dec 2022 none MIT — Details →
2.1.11 29 Nov 2022 none MIT — Details →
0.0.0-dev-20221128185230 28 Nov 2022 none MIT — Details →
0.0.0-dev-20221128183433 28 Nov 2022 none MIT — Details →
0.0.0-dev-20221128182021 28 Nov 2022 none MIT — Details →
0.0.0-dev-20221128164126 28 Nov 2022 none MIT — Details →
0.0.0-dev-20221124105520 24 Nov 2022 none MIT — Details →
0.0.0-dev-20221124103928 24 Nov 2022 none MIT — Details →
0.0.0-dev-20221123130515 23 Nov 2022 none MIT — Details →
0.0.0-dev-20221123123308 23 Nov 2022 none MIT — Details →
0.0.0-dev-20221122135803 22 Nov 2022 none MIT — Details →
0.0.0-dev-20221122115819 22 Nov 2022 none MIT — Details →
0.0.0-dev-20221117150258 17 Nov 2022 none MIT — Details →
0.0.0-dev-20221117065458 17 Nov 2022 none MIT — Details →
0.0.0-dev-20221116105413 16 Nov 2022 none MIT — Details →
0.0.0-dev-20221116103758 16 Nov 2022 none MIT — Details →
0.0.0-dev-20221116102301 16 Nov 2022 none MIT — Details →
0.0.0-dev-20221115102409 15 Nov 2022 none MIT — Details →
2.1.10 14 Nov 2022 none MIT — Details →
0.0.0-dev-20221108124603 08 Nov 2022 none MIT — Details →
0.0.0-dev-20221108100218 08 Nov 2022 none MIT — Details →
0.0.0-dev-20221108093520 08 Nov 2022 none MIT — Details →
0.0.0-dev-20221108090938 08 Nov 2022 none MIT — Details →
0.0.0-dev-20221108083411 08 Nov 2022 none MIT — Details →
0.0.0-dev-20221108075029 08 Nov 2022 none MIT — Details →
0.0.0-dev-20221108073543 08 Nov 2022 none MIT — Details →
0.0.0-dev-20221108071844 08 Nov 2022 none MIT — Details →
0.0.0-dev-20221107182607 07 Nov 2022 none MIT — Details →
0.0.0-dev-20221107181117 07 Nov 2022 none MIT — Details →
0.0.0-dev-20221107161407 07 Nov 2022 none MIT — Details →
2.1.9 17 Oct 2022 none — — Details →
0.0.0-dev-20221017063840 17 Oct 2022 none — — Details →
2.1.8 03 Oct 2022 none — — Details →
0.0.0-dev-20220929132459 29 Sep 2022 none — — Details →
0.0.0-dev-20220929105632 29 Sep 2022 none — — Details →
0.0.0-dev-20220926165450 26 Sep 2022 none — — Details →
0.0.0-dev-20220926164115 26 Sep 2022 none — — Details →
0.0.0-dev-20220922115811 22 Sep 2022 none — — Details →
0.0.0-dev-20220922114557 22 Sep 2022 none — — Details →
0.0.0-dev-20220921093814 21 Sep 2022 none — — Details →
0.0.0-dev-20220920121057 20 Sep 2022 none — — Details →
2.1.7 19 Sep 2022 none — — Details →
0.0.0-dev-20220919061024 19 Sep 2022 none — — Details →
0.0.0-dev-20220916164745 16 Sep 2022 none — — Details →
0.0.0-dev-20220916144141 16 Sep 2022 none — — Details →
0.0.0-dev-20220916141616 16 Sep 2022 none — — Details →
0.0.0-dev-20220916140800 16 Sep 2022 none — — Details →
0.0.0-dev-20220914105014 14 Sep 2022 none — — Details →
0.0.0-dev-20220914090509 14 Sep 2022 none — — Details →
0.0.0-dev-20220912133211 12 Sep 2022 none — — Details →

The newest 120 of 518 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 @chakra-ui/layout

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 @chakra-ui/layout

Is @chakra-ui/layout safe to use?

Vulert has no vulnerabilities on record for @chakra-ui/layout 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 @chakra-ui/layout's Vulert package health score?

Vulert scores @chakra-ui/layout 69/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 @chakra-ui/layout affected?

No. 2.3.1, 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.

Which version of @chakra-ui/layout should I use?

2.3.1 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does @chakra-ui/layout have?

0 vulnerabilities are recorded for @chakra-ui/layout 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 @chakra-ui/layout vulnerabilities disclosed?

0 vulnerabilities were recorded for @chakra-ui/layout 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 @chakra-ui/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 @chakra-ui/layout for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the @chakra-ui/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.