VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

react-docgen: vulnerability history, versions and safety

react-docgen 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 react-docgen vulnerabilities

Vulert verdict on react-docgen 8.0.4 i

Updated on 23 Oct 2026

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

Package health score 87/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

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

  • Current release 8.0.4 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 343 packages i
  • Stars 3,817 i
  • OpenSSF scorecard 6/10 i
  • Last release 1 month 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 react-docgen, 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
8.0.4 20 Sep 2026 none MIT — Details →
8.0.3 13 Mar 2026 none MIT — Details →
8.0.2 08 Oct 2025 none MIT — Details →
8.0.1 17 Aug 2025 none MIT — Details →
8.0.0 23 Apr 2025 none MIT — Details →
7.1.1 26 Jan 2025 none MIT — Details →
7.1.0 19 Oct 2024 none MIT — Details →
7.0.3 12 Jan 2024 none MIT — Details →
7.0.2 08 Jan 2024 none MIT — Details →
7.0.1 12 Nov 2023 none MIT — Details →
7.0.0 19 Oct 2023 none MIT — Details →
6.0.4 30 Aug 2023 none MIT — Details →
6.0.3 14 Aug 2023 none MIT — Details →
6.0.2 15 Jul 2023 none MIT — Details →
6.0.1 17 Jun 2023 none MIT — Details →
6.0.0 16 Jun 2023 none MIT — Details →
6.0.0-rc.9 20 May 2023 none MIT — Details →
6.0.0-rc.8 30 Apr 2023 none MIT — Details →
6.0.0-rc.7 30 Apr 2023 none MIT — Details →
6.0.0-beta.6 25 Mar 2023 none MIT — Details →
6.0.0-beta.5 31 Jan 2023 none MIT — Details →
6.0.0-alpha.4 15 Dec 2022 none MIT — Details →
5.4.3 02 Jul 2022 none MIT — Details →
5.4.2 13 Jun 2022 none MIT — Details →
6.0.0-alpha.3 13 Jun 2022 none MIT — Details →
5.4.1 28 May 2022 none MIT — Details →
6.0.0-alpha.2 04 Apr 2022 none MIT — Details →
6.0.0-alpha.1 04 Apr 2022 none MIT — Details →
6.0.0-alpha.0 08 May 2021 none MIT — Details →
5.4.0 08 May 2021 none MIT — Details →
5.4.0-alpha.0 21 Oct 2020 none MIT — Details →
5.3.1 21 Oct 2020 none MIT — Details →
5.3.0 26 Feb 2020 none MIT — Details →
5.2.1 13 Feb 2020 none MIT — Details →
5.2.0 06 Feb 2020 none MIT — Details →
5.1.0 05 Jan 2020 none MIT — Details →
5.0.0 11 Dec 2019 none MIT — Details →
5.0.0-beta.1 04 May 2019 none MIT — Details →
4.1.1 03 May 2019 none BSD-3-Clause — Details →
4.1.0 05 Mar 2019 none BSD-3-Clause — Details →
4.0.1 25 Feb 2019 none BSD-3-Clause — Details →
4.0.0 15 Feb 2019 none BSD-3-Clause — Details →
3.0.0 28 Jan 2019 none BSD-3-Clause — Details →
3.0.0-rc.2 03 Nov 2018 none BSD-3-Clause — Details →
3.0.0-rc.1 26 Aug 2018 none BSD-3-Clause — Details →
3.0.0-rc.0 14 Jul 2018 none BSD-3-Clause — Details →
2.21.0 26 Jun 2018 none BSD-3-Clause — Details →
3.0.0-beta12 12 Apr 2018 none BSD-3-Clause — Details →
3.0.0-beta11 17 Feb 2018 none BSD-3-Clause — Details →
2.20.1 17 Feb 2018 none BSD-3-Clause — Details →
3.0.0-beta10 23 Jan 2018 none BSD-3-Clause — Details →
3.0.0-beta9 09 Nov 2017 none BSD-3-Clause — Details →
2.20.0 09 Nov 2017 none BSD-3-Clause — Details →
3.0.0-beta8 11 Oct 2017 none BSD-3-Clause — Details →
2.19.0 11 Oct 2017 none BSD-3-Clause — Details →
3.0.0-beta7 05 Sep 2017 none BSD-3-Clause — Details →
2.18.0 05 Sep 2017 none BSD-3-Clause — Details →
3.0.0-beta6 22 Jul 2017 none BSD-3-Clause — Details →
2.17.0 21 Jul 2017 none BSD-3-Clause — Details →
3.0.0-beta5 15 Jun 2017 none BSD-3-Clause — Details →
2.16.0 14 Jun 2017 none BSD-3-Clause — Details →
3.0.0-beta4 03 May 2017 none BSD-3-Clause — Details →
2.15.0 03 May 2017 none BSD-3-Clause — Details →
2.14.1 18 Apr 2017 none BSD-3-Clause — Details →
3.0.0-beta3 13 Apr 2017 none BSD-3-Clause — Details →
2.14.0 13 Apr 2017 none BSD-3-Clause — Details →
3.0.0-beta2 17 Mar 2017 none BSD-3-Clause — Details →
3.0.0-beta1 17 Mar 2017 none BSD-3-Clause — Details →
2.13.0 22 Dec 2016 none BSD-3-Clause — Details →
2.12.1 21 Oct 2016 none BSD-3-Clause — Details →
2.12.0 20 Oct 2016 none BSD-3-Clause — Details →
2.11.0 05 Oct 2016 none BSD-3-Clause — Details →
2.10.0 25 Aug 2016 none BSD-3-Clause — Details →
2.9.1 22 Jun 2016 none BSD-3-Clause — Details →
2.9.0 21 Jun 2016 none BSD-3-Clause — Details →
2.8.2 10 Apr 2016 none BSD-3-Clause — Details →
2.8.1 08 Apr 2016 none BSD-3-Clause — Details →
2.8.0 08 Apr 2016 none BSD-3-Clause — Details →
2.7.0 29 Jan 2016 none BSD-3-Clause — Details →
2.6.3 19 Jan 2016 none BSD-3-Clause — Details →
2.6.2 19 Jan 2016 none BSD-3-Clause — Details →
2.6.1 12 Jan 2016 none BSD-3-Clause — Details →
2.6.0 05 Jan 2016 none BSD-3-Clause — Details →
2.5.0 04 Jan 2016 none BSD-3-Clause — Details →
2.4.0 30 Oct 2015 none BSD-3-Clause — Details →
2.3.1 20 Oct 2015 none BSD-3-Clause — Details →
2.3.0 20 Oct 2015 none BSD-3-Clause — Details →
2.2.0 28 Sep 2015 none BSD-3-Clause — Details →
2.1.2 04 Sep 2015 none BSD-3-Clause — Details →
2.1.1 04 Sep 2015 none BSD-3-Clause — Details →
2.1.0 01 Sep 2015 none BSD-3-Clause — Details →
2.0.1 31 Aug 2015 none BSD-3-Clause — Details →
2.0.0 24 Jul 2015 none BSD-3-Clause — Details →
1.3.0 18 May 2015 none BSD-3-Clause — Details →
1.2.0 03 Apr 2015 none BSD-3-Clause — Details →
1.1.0 19 Mar 2015 none BSD-3-Clause — Details →
1.0.2 17 Mar 2015 none BSD-3-Clause — Details →
1.0.1 17 Mar 2015 none BSD-3-Clause — Details →
1.0.0 16 Mar 2015 none BSD-3-Clause — Details →

All 99 versions Vulert tracks for this package. 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 react-docgen

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 react-docgen

Is react-docgen safe to use?

Vulert has no vulnerabilities on record for react-docgen 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 react-docgen's Vulert package health score?

Vulert scores react-docgen 87/100, which reads as healthy. 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 react-docgen affected?

No. 8.0.4, 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 react-docgen should I use?

8.0.4 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 react-docgen have?

0 vulnerabilities are recorded for react-docgen 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 react-docgen vulnerabilities disclosed?

0 vulnerabilities were recorded for react-docgen 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 react-docgen 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 react-docgen for upcoming vulnerabilities?

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