Vulnerability Database · npm · Package report
@chakra-ui/hooks: vulnerability history, versions and safety
@chakra-ui/hooks is a package in the npm ecosystem. Vulert holds no vulnerabilities for it yet.
Nothing recorded for this package in the npm ecosystem.
Every vulnerability has a patched version to move to.
No published version shipped hostile code.
Vulert verdict on @chakra-ui/hooks 2.4.2 i
Updated on 23 Oct 2026
Good news: 2.4.2, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Maintaining
- Popularity Widely used
- Community Moderate
What to do: Stay on 2.4.2 or newer. This can change: a vulnerability disclosed tomorrow can affect 2.4.2 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release 2.4.2 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Depended on by 12 packages i
- Stars 40,698 i
- OpenSSF scorecard 4/10 i
- Last release 24 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/hooks, 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.
- 2.4.6 04 Jun 2026
- 2.4.5 14 May 2025
- 2.4.4 19 Feb 2025
- 2.4.3 07 Nov 2024
- 0.0.0-v2-latest-20241107153126 07 Nov 2024
- 2.4.2 09 Oct 2024
- 2.4.1 04 Oct 2024
- 2.4.0 04 Oct 2024
- 2.3.3 03 Oct 2024
- 2.3.2 02 Oct 2024
- 0.0.0-v2-latest-20241002175335 02 Oct 2024
- 0.0.0-v2-latest-20241002174536 02 Oct 2024
- 0.0.0-v2-latest-20241002170600 02 Oct 2024
- 2.3.1 01 Oct 2024
- 2.3.0 01 Oct 2024
- 0.0.0-v2-latest-20241001130949 01 Oct 2024
- 0.0.0-v2-latest-20241001124626 01 Oct 2024
- 0.0.0-v2-latest-20241001120143 01 Oct 2024
- 0.0.0-20241001114637 01 Oct 2024
- 2.2.2 30 Sep 2024
- 3.0.0-next.23 06 Sep 2024
- 3.0.0-next.22 04 Sep 2024
- 3.0.0-next.21 03 Sep 2024
- 3.0.0-next.20 27 Aug 2024
- 3.0.0-next.19 26 Aug 2024
- 3.0.0-next.18 23 Aug 2024
- 3.0.0-next.17 22 Aug 2024
- 3.0.0-next.16 18 Aug 2024
- 3.0.0-next.15 16 Aug 2024
- 3.0.0-next.14 16 Aug 2024
- 3.0.0-next.13 08 Aug 2024
- 3.0.0-next.12 30 Jul 2024
- 3.0.0-next.11 09 Jul 2024
- 3.0.0-next.10 29 Jun 2024
- 3.0.0-next.9 28 Jun 2024
- 3.0.0-next.8 22 Jun 2024
- 3.0.0-next.7 21 Jun 2024
- 3.0.0-next.6 20 Jun 2024
- 3.0.0-next.5 17 Jun 2024
- 3.0.0-next.4 03 Jun 2024
- 3.0.0-next.3 02 Jun 2024
- 3.0.0-next.2 01 Jun 2024
- 3.0.0-next.1 30 May 2024
- 3.0.0-next.0 24 May 2024
- 0.0.0-dev-20240315145938 15 Mar 2024
- 0.0.0-dev-20240314210302 14 Mar 2024
- 0.0.0-dev-20240311162014 11 Mar 2024
- 0.0.0-dev-20240228132430 28 Feb 2024
- 0.0.0-dev-20240224210122 24 Feb 2024
- 0.0.0-dev-20240224205404 24 Feb 2024
- 0.0.0-dev-20240115120705 15 Jan 2024
- 0.0.0-dev-20240112001210 12 Jan 2024
- 0.0.0-dev-20240110191159 10 Jan 2024
- 0.0.0-v3-20240109123510 09 Jan 2024
- 2.2.1 08 Sep 2023
- 0.0.0-dev-20230908144305 08 Sep 2023
- 0.0.0-dev-20230830133821 30 Aug 2023
- 2.2.0 25 Apr 2023
- 0.0.0-dev-20230424225650 24 Apr 2023
- 0.0.0-dev-20230424222806 24 Apr 2023
- 0.0.0-dev-20230424221053 24 Apr 2023
- 0.0.0-dev-20230424210540 24 Apr 2023
- 0.0.0-dev-20230424205150 24 Apr 2023
- 0.0.0-dev-20230424202839 24 Apr 2023
- 0.0.0-dev-20230424201223 24 Apr 2023
- 0.0.0-dev-20230424194913 24 Apr 2023
- 0.0.0-dev-20230424191827 24 Apr 2023
- 0.0.0-dev-20230424190033 24 Apr 2023
- 0.0.0-dev-20230423230056 23 Apr 2023
- 0.0.0-dev-20230422142907 22 Apr 2023
- 0.0.0-dev-20230421204125 21 Apr 2023
- 2.1.6 13 Feb 2023
- 0.0.0-dev-20230213131136 13 Feb 2023
- 0.0.0-dev-20230213124817 13 Feb 2023
- 0.0.0-dev-20230213123249 13 Feb 2023
- 0.0.0-dev-20230208114919 08 Feb 2023
- 0.0.0-dev-20230208112929 08 Feb 2023
- 0.0.0-dev-20230207153012 07 Feb 2023
- 0.0.0-dev-20230207150933 07 Feb 2023
- 0.0.0-dev-20230206162801 06 Feb 2023
- 0.0.0-dev-20230206161237 06 Feb 2023
- 0.0.0-dev-20230206143950 06 Feb 2023
- 0.0.0-dev-20230206142400 06 Feb 2023
- 0.0.0-dev-20230206135638 06 Feb 2023
- 2.1.5 12 Jan 2023
- 0.0.0-dev-20230112154520 12 Jan 2023
- 0.0.0-dev-20230112152756 12 Jan 2023
- 0.0.0-dev-20230112145104 12 Jan 2023
- 0.0.0-dev-20230112143332 12 Jan 2023
- 0.0.0-dev-20230112141201 12 Jan 2023
- 0.0.0-dev-20230112113621 12 Jan 2023
- 0.0.0-dev-20230111211417 11 Jan 2023
- 2.1.4 29 Dec 2022
- 0.0.0-dev-20221229212737 29 Dec 2022
- 0.0.0-dev-20221229203627 29 Dec 2022
- 0.0.0-dev-20221229202029 29 Dec 2022
- 0.0.0-dev-20221229200356 29 Dec 2022
- 2.1.3 26 Dec 2022
- 0.0.0-dev-20221223180742 23 Dec 2022
- 0.0.0-dev-20221222051548 22 Dec 2022
- 0.0.0-dev-20221221152939 21 Dec 2022
- 0.0.0-dev-20221221133224 21 Dec 2022
- 0.0.0-dev-20221221110721 21 Dec 2022
- 2.1.2 14 Nov 2022
- 0.0.0-dev-20221108124603 08 Nov 2022
- 0.0.0-dev-20221108100218 08 Nov 2022
- 0.0.0-dev-20221108093520 08 Nov 2022
- 0.0.0-dev-20221108090938 08 Nov 2022
- 0.0.0-dev-20221108083411 08 Nov 2022
- 0.0.0-dev-20221108075029 08 Nov 2022
- 0.0.0-dev-20221108073543 08 Nov 2022
- 0.0.0-dev-20221108071844 08 Nov 2022
- 0.0.0-dev-20221107182607 07 Nov 2022
- 0.0.0-dev-20221107181117 07 Nov 2022
- 0.0.0-dev-20221107161407 07 Nov 2022
- 2.1.1 02 Nov 2022
- 0.0.0-dev-20221102152926 02 Nov 2022
- 0.0.0-dev-20221102143239 02 Nov 2022
- 0.0.0-dev-20221102124227 02 Nov 2022
- 0.0.0-dev-20221102123311 02 Nov 2022
The newest 120 of 421 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.
Other ways into the data
03 Vulnerabilities
Recorded vulnerabilities for @chakra-ui/hooks
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
Questions
About @chakra-ui/hooks
Is @chakra-ui/hooks safe to use?
Vulert has no vulnerabilities on record for @chakra-ui/hooks 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/hooks's Vulert package health score?
Vulert scores @chakra-ui/hooks 76/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 @chakra-ui/hooks affected?
No. 2.4.2, 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/hooks should I use?
2.4.2 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/hooks have?
0 vulnerabilities are recorded for @chakra-ui/hooks 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/hooks vulnerabilities disclosed?
0 vulnerabilities were recorded for @chakra-ui/hooks 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/hooks 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/hooks for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the @chakra-ui/hooks version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.