VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

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

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

Vulert verdict on @chakra-ui/progress 2.2.0 i

Updated on 23 Oct 2026

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

  • Current release 2.2.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 61 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/progress, 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.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.1.6 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.5 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.4 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.3 26 Dec 2022 none MIT — Details →
0.0.0-dev-20221223180742 23 Dec 2022 none MIT — Details →
2.1.2 06 Dec 2022 none MIT — Details →
0.0.0-dev-20221206151209 06 Dec 2022 none MIT — Details →
2.1.1 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.0 02 Nov 2022 none MIT — Details →
0.0.0-dev-20221102152926 02 Nov 2022 none MIT — Details →
0.0.0-dev-20221102143239 02 Nov 2022 none MIT — Details →
0.0.0-dev-20221102124227 02 Nov 2022 none MIT — Details →
0.0.0-dev-20221102123311 02 Nov 2022 none MIT — Details →
0.0.0-dev-20221101183810 01 Nov 2022 none MIT — Details →
0.0.0-dev-20221101182032 01 Nov 2022 none MIT — Details →
0.0.0-dev-20221031131135 31 Oct 2022 none MIT — Details →
0.0.0-dev-20221027041741 27 Oct 2022 none MIT — Details →
0.0.0-dev-20221027040551 27 Oct 2022 none MIT — Details →
2.0.12 17 Oct 2022 none MIT — Details →
0.0.0-dev-20221017063840 17 Oct 2022 none MIT — Details →
2.0.11 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.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 →
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 →
0.0.0-dev-20220810132240 10 Aug 2022 none MIT — Details →
0.0.0-dev-20220810124358 10 Aug 2022 none MIT — Details →
0.0.0-dev-20220810122556 10 Aug 2022 none MIT — Details →
0.0.0-dev-20220810121727 10 Aug 2022 none MIT — Details →
0.0.0-dev-20220810112922 10 Aug 2022 none MIT — Details →
0.0.0-dev-20220810053106 10 Aug 2022 none MIT — Details →
0.0.0-dev-20220808090501 08 Aug 2022 none MIT — Details →
0.0.0-dev-20220808075419 08 Aug 2022 none MIT — Details →
2.0.7 05 Aug 2022 none MIT — Details →
0.0.0-dev-20220805062318 05 Aug 2022 none — — Details →
0.0.0-dev-20220804200605 04 Aug 2022 none — — Details →
0.0.0-dev-20220804194739 04 Aug 2022 none — — Details →
0.0.0-dev-20220804193815 04 Aug 2022 none — — Details →
0.0.0-dev-20220804193103 04 Aug 2022 none — — Details →
2.0.6 25 Jul 2022 none — — Details →
2.0.5 13 Jul 2022 none — — Details →
0.0.0-dev-202261317818 13 Jul 2022 none — — Details →
0.0.0-dev-202261316456 13 Jul 2022 none — — 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 21 Jun 2022 none — — Details →

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.

03 Vulnerabilities

Recorded vulnerabilities for @chakra-ui/progress

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

Is @chakra-ui/progress safe to use?

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

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

No. 2.2.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/progress should I use?

2.2.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/progress have?

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

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

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