VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

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

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

Vulert verdict on @chakra-ui/theme-tools 2.2.6 i

Updated on 23 Oct 2026

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

Package health score 78/100
  • Security Minor issues
  • Maintenance Maintaining
  • Popularity Key ecosystem project
  • Community Moderate

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

  • Current release 2.2.6 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 160 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/theme-tools, 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.2.10 04 Jun 2026 none MIT — Details →
2.2.9 14 May 2025 none MIT — Details →
2.2.8 19 Feb 2025 none MIT — Details →
2.2.7 07 Nov 2024 none MIT — Details →
0.0.0-v2-latest-20241107153126 07 Nov 2024 none MIT — Details →
2.2.6 09 Oct 2024 none MIT — Details →
2.2.5 04 Oct 2024 none MIT — Details →
2.2.4 04 Oct 2024 none MIT — Details →
2.2.3 03 Oct 2024 none MIT — Details →
2.2.2 02 Oct 2024 none MIT — Details →
0.0.0-v2-latest-20241002175335 02 Oct 2024 none MIT — Details →
0.0.0-v2-latest-20241002174536 02 Oct 2024 none MIT — Details →
0.0.0-v2-latest-20241002170600 02 Oct 2024 none MIT — Details →
2.2.1 01 Oct 2024 none MIT — Details →
2.2.0 01 Oct 2024 none MIT — Details →
0.0.0-v2-latest-20241001130949 01 Oct 2024 none MIT — Details →
0.0.0-dev-20240315145938 15 Mar 2024 none MIT — Details →
0.0.0-dev-20240314210302 14 Mar 2024 none MIT — Details →
0.0.0-dev-20240311162014 11 Mar 2024 none MIT — Details →
0.0.0-dev-20240228132430 28 Feb 2024 none MIT — Details →
0.0.0-dev-20240224210122 24 Feb 2024 none MIT — Details →
0.0.0-dev-20240224205404 24 Feb 2024 none MIT — Details →
0.0.0-dev-20240115120705 15 Jan 2024 none MIT — Details →
0.0.0-dev-20240112001210 12 Jan 2024 none MIT — Details →
0.0.0-dev-20240110191159 10 Jan 2024 none MIT — Details →
0.0.0-v3-20240109123510 09 Jan 2024 none MIT — Details →
2.1.2 09 Nov 2023 none MIT — Details →
0.0.0-dev-20231109134954 09 Nov 2023 none MIT — Details →
0.0.0-dev-20231109130949 09 Nov 2023 none MIT — Details →
2.1.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 →
0.0.0-dev-20230820153451 20 Aug 2023 none MIT — Details →
0.0.0-dev-20230815225224 15 Aug 2023 none MIT — Details →
0.0.0-dev-20230815223317 15 Aug 2023 none MIT — 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 →
0.0.0-dev-20230716142935 16 Jul 2023 none MIT — Details →
0.0.0-dev-20230716141052 16 Jul 2023 none MIT — Details →
0.0.0-dev-20230714214323 14 Jul 2023 none MIT — Details →
0.0.0-dev-20230714212045 14 Jul 2023 none MIT — Details →
0.0.0-dev-20230711204333 11 Jul 2023 none MIT — Details →
2.0.18 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 →
0.0.0-dev-20230528173059 28 May 2023 none MIT — Details →
0.0.0-dev-20230528170051 28 May 2023 none MIT — Details →
0.0.0-dev-20230528164120 28 May 2023 none MIT — Details →
0.0.0-dev-20230528160711 28 May 2023 none MIT — Details →
0.0.0-dev-20230528143537 28 May 2023 none MIT — Details →
0.0.0-dev-20230528140259 28 May 2023 none MIT — Details →
0.0.0-dev-20230528132208 28 May 2023 none MIT — Details →
2.0.17 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.16 29 Dec 2022 none MIT — Details →
0.0.0-dev-20221229212737 29 Dec 2022 none MIT — Details →
0.0.0-dev-20221229203627 29 Dec 2022 none MIT — Details →
0.0.0-dev-20221229202029 29 Dec 2022 none MIT — Details →
0.0.0-dev-20221229200356 29 Dec 2022 none MIT — Details →
0.0.0-dev-20221229143302 29 Dec 2022 none MIT — Details →
0.0.0-dev-20221229141945 29 Dec 2022 none MIT — Details →
0.0.0-dev-20221228093251 28 Dec 2022 none MIT — Details →
0.0.0-dev-20221228081854 28 Dec 2022 none MIT — Details →
0.0.0-dev-20221228075207 28 Dec 2022 none MIT — Details →
2.0.15 26 Dec 2022 none MIT — Details →
0.0.0-dev-20221223180742 23 Dec 2022 none MIT — Details →
2.0.14 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 →
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 — — Details →
0.0.0-dev-20221108075029 08 Nov 2022 none — — Details →
0.0.0-dev-20221108073543 08 Nov 2022 none — — Details →
0.0.0-dev-20221108071844 08 Nov 2022 none — — Details →
0.0.0-dev-20221107182607 07 Nov 2022 none — — Details →
0.0.0-dev-20221107181117 07 Nov 2022 none — — Details →
0.0.0-dev-20221107161407 07 Nov 2022 none — — Details →
2.0.12 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.0.11 29 Aug 2022 none — — Details →
0.0.0-dev-20220829143113 29 Aug 2022 none — — Details →
0.0.0-dev-20220829121234 29 Aug 2022 none — — Details →
0.0.0-dev-20220829120312 29 Aug 2022 none — — Details →

The newest 120 of 495 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/theme-tools

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/theme-tools

Is @chakra-ui/theme-tools safe to use?

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

Vulert scores @chakra-ui/theme-tools 78/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/theme-tools affected?

No. 2.2.6, 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/theme-tools should I use?

2.2.6 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/theme-tools have?

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

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

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