VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

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

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

Vulert verdict on @chakra-ui/provider 2.4.2 i

Updated on 23 Oct 2026

Good news: 2.4.2, 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.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 46 packages i
  • Stars 40,698 i
  • OpenSSF scorecard 4/10 i
  • Last release 35 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/provider, 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
0.0.0-dev-20231123223450 23 Nov 2023 none MIT — Details →
0.0.0-dev-20231113225212 13 Nov 2023 none MIT — Details →
2.4.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.4.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.4.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.3.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 →
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 →
0.0.0-dev-20230528125234 28 May 2023 none MIT — Details →
0.0.0-dev-20230528123435 28 May 2023 none MIT — Details →
0.0.0-dev-20230509101921 09 May 2023 none MIT — Details →
2.2.4 03 May 2023 none MIT — Details →
0.0.0-dev-20230502211538 02 May 2023 none MIT — Details →
0.0.0-dev-20230502164338 02 May 2023 none MIT — Details →
0.0.0-dev-20230502162309 02 May 2023 none MIT — Details →
0.0.0-dev-20230502155235 02 May 2023 none MIT — Details →
0.0.0-dev-20230502144229 02 May 2023 none MIT — Details →
2.2.3 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 →
0.0.0-dev-20230424194913 24 Apr 2023 none MIT — Details →
0.0.0-dev-20230424191827 24 Apr 2023 none MIT — Details →
0.0.0-dev-20230424190033 24 Apr 2023 none MIT — Details →
0.0.0-dev-20230423230056 23 Apr 2023 none MIT — Details →
0.0.0-dev-20230422142907 22 Apr 2023 none MIT — Details →
0.0.0-dev-20230421204125 21 Apr 2023 none MIT — Details →
0.0.0-dev-20230417150059 17 Apr 2023 none MIT — Details →
0.0.0-dev-20230417144407 17 Apr 2023 none MIT — Details →
0.0.0-dev-20230403120345 03 Apr 2023 none MIT — Details →
0.0.0-dev-20230403072857 03 Apr 2023 none MIT — Details →
2.2.2 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 →
0.0.0-dev-20230327175739 27 Mar 2023 none MIT — Details →
2.2.1 27 Mar 2023 none MIT — Details →
0.0.0-dev-20230326141955 26 Mar 2023 none MIT — Details →
0.0.0-dev-20230323211647 23 Mar 2023 none MIT — Details →
0.0.0-dev-20230323205240 23 Mar 2023 none MIT — Details →
0.0.0-dev-20230323203724 23 Mar 2023 none MIT — Details →
2.2.0 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 →
0.0.0-dev-20230319202046 19 Mar 2023 none MIT — Details →
0.0.0-dev-20230319193708 19 Mar 2023 none MIT — Details →
0.0.0-dev-20230319192154 19 Mar 2023 none MIT — Details →
0.0.0-dev-20230318183840 18 Mar 2023 none MIT — Details →
0.0.0-dev-20230318182221 18 Mar 2023 none MIT — Details →
0.0.0-dev-20230318180604 18 Mar 2023 none MIT — Details →
0.0.0-dev-20230318173550 18 Mar 2023 none MIT — Details →
0.0.0-dev-20230318171948 18 Mar 2023 none MIT — Details →
0.0.0-dev-20230318162751 18 Mar 2023 none MIT — Details →
0.0.0-dev-20230318150808 18 Mar 2023 none MIT — Details →
2.1.3 17 Mar 2023 none MIT — Details →
0.0.0-dev-20230317190235 17 Mar 2023 none MIT — Details →
0.0.0-dev-20230317141833 17 Mar 2023 none MIT — Details →
2.1.2 15 Feb 2023 none MIT — Details →
0.0.0-dev-20230215112011 15 Feb 2023 none — — Details →
2.1.1 13 Feb 2023 none — — Details →
0.0.0-dev-20230213131136 13 Feb 2023 none — — Details →
0.0.0-dev-20230213124817 13 Feb 2023 none — — Details →
0.0.0-dev-20230213123249 13 Feb 2023 none — — Details →
0.0.0-dev-20230208114919 08 Feb 2023 none — — Details →
0.0.0-dev-20230208112929 08 Feb 2023 none — — Details →
0.0.0-dev-20230207153012 07 Feb 2023 none — — Details →
0.0.0-dev-20230207150933 07 Feb 2023 none — — Details →
0.0.0-dev-20230206162801 06 Feb 2023 none — — Details →
0.0.0-dev-20230206161237 06 Feb 2023 none — — Details →
0.0.0-dev-20230206143950 06 Feb 2023 none — — Details →
0.0.0-dev-20230206142400 06 Feb 2023 none — — Details →
0.0.0-dev-20230206135638 06 Feb 2023 none — — Details →
0.0.0-dev-20230206134100 06 Feb 2023 none — — Details →
0.0.0-dev-20230206132511 06 Feb 2023 none — — Details →
2.1.0 16 Jan 2023 none — — Details →
0.0.0-dev-20230116124502 16 Jan 2023 none — — Details →
0.0.0-dev-20230116122157 16 Jan 2023 none — — Details →
0.0.0-dev-20230116120206 16 Jan 2023 none — — Details →

The newest 120 of 606 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/provider

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/provider

Is @chakra-ui/provider safe to use?

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

Vulert scores @chakra-ui/provider 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/provider 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/provider 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/provider have?

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

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

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