VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

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

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

Vulert verdict on @chakra-ui/focus-lock 2.1.0 i

Updated on 23 Oct 2026

Good news: 2.1.0, 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.1.0 or newer. This can change: a vulnerability disclosed tomorrow can affect 2.1.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 2.1.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 66 packages i
  • Stars 40,698 i
  • OpenSSF scorecard 4/10 i
  • Last release 39 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/focus-lock, 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.1.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.0.17 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 →
2.0.16 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.0.15 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.0.14 26 Dec 2022 none MIT — Details →
0.0.0-dev-20221223180742 23 Dec 2022 none MIT — Details →
2.0.13 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.0.12 03 Oct 2022 none MIT — Details →
0.0.0-dev-20220929132459 29 Sep 2022 none MIT — Details →
0.0.0-dev-20220929105632 29 Sep 2022 none MIT — Details →
0.0.0-dev-20220926165450 26 Sep 2022 none MIT — Details →
0.0.0-dev-20220926164115 26 Sep 2022 none MIT — Details →
0.0.0-dev-20220922115811 22 Sep 2022 none MIT — Details →
0.0.0-dev-20220922114557 22 Sep 2022 none MIT — Details →
0.0.0-dev-20220921093814 21 Sep 2022 none MIT — Details →
0.0.0-dev-20220920121057 20 Sep 2022 none MIT — Details →
2.0.11 19 Sep 2022 none MIT — Details →
0.0.0-dev-20220919061024 19 Sep 2022 none MIT — Details →
0.0.0-dev-20220916164745 16 Sep 2022 none MIT — Details →
0.0.0-dev-20220916144141 16 Sep 2022 none MIT — Details →
0.0.0-dev-20220916141616 16 Sep 2022 none MIT — Details →
2.0.10 24 Aug 2022 none MIT — Details →
0.0.0-dev-20220824082222 24 Aug 2022 none MIT — Details →
0.0.0-dev-20220824080240 24 Aug 2022 none MIT — Details →
0.0.0-dev-20220824074122 24 Aug 2022 none MIT — Details →
0.0.0-dev-20220823195046 23 Aug 2022 none MIT — Details →
0.0.0-dev-20220823192757 23 Aug 2022 none MIT — Details →
0.0.0-dev-20220823165602 23 Aug 2022 none MIT — Details →
0.0.0-dev-20220823150801 23 Aug 2022 none MIT — Details →
0.0.0-dev-20220822184448 22 Aug 2022 none MIT — Details →
0.0.0-dev-20220822103611 22 Aug 2022 none MIT — Details →
0.0.0-dev-20220822055339 22 Aug 2022 none MIT — Details →
0.0.0-dev-20220822054045 22 Aug 2022 none MIT — Details →
0.0.0-dev-20220822051456 22 Aug 2022 none MIT — Details →
0.0.0-dev-20220820195548 20 Aug 2022 none MIT — Details →
0.0.0-dev-20220820193723 20 Aug 2022 none MIT — Details →
0.0.0-dev-20220820185458 20 Aug 2022 none MIT — Details →
0.0.0-dev-20220820173639 20 Aug 2022 none MIT — Details →
0.0.0-dev-20220820172220 20 Aug 2022 none MIT — Details →
0.0.0-dev-20220820165925 20 Aug 2022 none MIT — Details →
0.0.0-dev-20220820152257 20 Aug 2022 none MIT — Details →
0.0.0-dev-20220820124231 20 Aug 2022 none MIT — Details →
0.0.0-dev-20220820120308 20 Aug 2022 none MIT — Details →
0.0.0-dev-20220819191103 19 Aug 2022 none MIT — Details →
0.0.0-dev-20220819143632 19 Aug 2022 none MIT — Details →
0.0.0-dev-20220819142048 19 Aug 2022 none MIT — Details →
2.0.9 14 Aug 2022 none MIT — Details →
2.0.8 13 Aug 2022 none MIT — Details →
0.0.0-dev-20220813083358 13 Aug 2022 none MIT — Details →
0.0.0-dev-20220813070741 13 Aug 2022 none MIT — Details →
0.0.0-dev-20220813063717 13 Aug 2022 none MIT — Details →
0.0.0-dev-20220813055957 13 Aug 2022 none MIT — Details →
0.0.0-dev-20220813053727 13 Aug 2022 none MIT — Details →
0.0.0-dev-20220813052715 13 Aug 2022 none MIT — Details →
0.0.0-dev-20220813051625 13 Aug 2022 none MIT — Details →
0.0.0-dev-20220812060931 12 Aug 2022 none MIT — Details →
0.0.0-dev-20220811160709 11 Aug 2022 none MIT — Details →
0.0.0-dev-20220811093515 11 Aug 2022 none MIT — Details →
0.0.0-dev-20220811084042 11 Aug 2022 none MIT — Details →
2.0.7 05 Aug 2022 none MIT — Details →
0.0.0-dev-20220805062318 05 Aug 2022 none MIT — Details →
0.0.0-dev-20220804200605 04 Aug 2022 none MIT — Details →
0.0.0-dev-20220804194739 04 Aug 2022 none MIT — Details →
0.0.0-dev-20220804193815 04 Aug 2022 none MIT — Details →
0.0.0-dev-20220804193103 04 Aug 2022 none MIT — Details →
2.0.6 25 Jul 2022 none MIT — Details →
2.0.5 13 Jul 2022 none MIT — Details →
0.0.0-dev-202261317818 13 Jul 2022 none MIT — Details →
0.0.0-dev-202261316456 13 Jul 2022 none MIT — Details →
0.0.0-dev-2022612222012 12 Jul 2022 none — — Details →
2.0.4 10 Jul 2022 none — — Details →
0.0.0-dev-2022610103924 10 Jul 2022 none — — Details →
0.0.0-dev-2022610103716 10 Jul 2022 none — — Details →
0.0.0-dev-202268165050 08 Jul 2022 none — — Details →
0.0.0-dev-202268163535 08 Jul 2022 none — — Details →
0.0.0-dev-2022669710 06 Jul 2022 none — — Details →
0.0.0-dev-2022659431 05 Jul 2022 none — — Details →
0.0.0-dev-2022659325 05 Jul 2022 none — — Details →
0.0.0-dev-202264144818 04 Jul 2022 none — — Details →
2.0.3 06 Jun 2022 none — — Details →
0.0.0-dev-202256192154 06 Jun 2022 none — — Details →
2.0.2 24 May 2022 none — — Details →
0.0.0-dev-202242481651 24 May 2022 none — — Details →
0.0.0-dev-20224248516 24 May 2022 none — — Details →
0.0.0-dev-20224248246 24 May 2022 none — — Details →
0.0.0-dev-2022423121615 23 May 2022 none — — Details →
0.0.0-dev-2022423121532 23 May 2022 none — — Details →
2.0.1 22 May 2022 none — — Details →
0.0.0-dev-202242121518 21 May 2022 none — — Details →

The newest 120 of 258 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/focus-lock

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/focus-lock

Is @chakra-ui/focus-lock safe to use?

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

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

No. 2.1.0, 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/focus-lock should I use?

2.1.0 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/focus-lock have?

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

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

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