VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

react-mentions: vulnerability history, versions and safety

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

Vulert verdict on react-mentions 4.4.10 i

Updated on 23 Oct 2026

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

Package health score 45/100
  • Security No known security issues
  • Maintenance Deprecated
  • Popularity Widely used
  • Community Active

The registry marks the latest release as deprecated, which caps this score.

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

  • Current release 4.4.10 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 321 packages i
  • Stars 2,689 i
  • Last release 39 months ago i
  • Licence BSD-3-Clause 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-mentions, 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
4.4.10 30 Jun 2023 none BSD-3-Clause — Details →
4.4.9 05 Jun 2023 none BSD-3-Clause — Details →
4.4.8 01 Jun 2023 none BSD-3-Clause — Details →
4.4.7 19 Jul 2022 none BSD-3-Clause — Details →
4.4.6 11 Jul 2022 none BSD-3-Clause — Details →
4.4.5 08 Jul 2022 none BSD-3-Clause — Details →
4.4.4 27 Jun 2022 none BSD-3-Clause — Details →
4.4.2 30 May 2022 none BSD-3-Clause — Details →
4.4.1 27 May 2022 none BSD-3-Clause — Details →
4.4.0 27 May 2022 none BSD-3-Clause — Details →
4.3.2 20 Apr 2022 none BSD-3-Clause — Details →
4.3.1 20 Jan 2022 none BSD-3-Clause — Details →
4.3.0 25 May 2021 none BSD-3-Clause — Details →
4.2.0 20 May 2021 none BSD-3-Clause — Details →
4.1.1 14 Jan 2021 none BSD-3-Clause — Details →
4.1.0 07 Jan 2021 none BSD-3-Clause — Details →
4.0.2 14 Aug 2020 none BSD-3-Clause — Details →
4.0.1 09 Jul 2020 none BSD-3-Clause — Details →
4.0.0 18 Jun 2020 none BSD-3-Clause — Details →
3.3.2 16 Jun 2020 none BSD-3-Clause — Details →
3.3.1 17 Oct 2019 none BSD-3-Clause — Details →
3.3.0 11 Oct 2019 none BSD-3-Clause — Details →
3.2.0 09 Oct 2019 none BSD-3-Clause — Details →
3.1.1 14 Aug 2019 none BSD-3-Clause — Details →
3.1.0 27 Jul 2019 none BSD-3-Clause — Details →
3.0.2 05 Jun 2019 none BSD-3-Clause — Details →
3.0.1 27 May 2019 none BSD-3-Clause — Details →
3.0.0 23 Apr 2019 none BSD-3-Clause — Details →
2.4.2 21 Feb 2019 none BSD-3-Clause — Details →
2.4.1 15 Nov 2018 none BSD-3-Clause — Details →
2.4.0 06 Nov 2018 none BSD-3-Clause — Details →
2.3.1 02 Oct 2018 none BSD-3-Clause — Details →
2.3.0 07 Sep 2018 none BSD-3-Clause — Details →
2.2.0 04 Sep 2018 none BSD-3-Clause — Details →
2.1.1 29 Aug 2018 none BSD-3-Clause — Details →
2.1.0 27 Jul 2018 none BSD-3-Clause — Details →
2.0.1 09 Mar 2018 none BSD-3-Clause — Details →
2.0.0 06 Mar 2018 none BSD-3-Clause — Details →
1.2.2 13 Jan 2018 none BSD-3-Clause — Details →
1.2.1 06 Sep 2017 none BSD-3-Clause — Details →
1.2.0 13 Jun 2017 none BSD-3-Clause — Details →
1.1.0 28 Apr 2017 none BSD-3-Clause — Details →
1.0.1 19 Apr 2017 none BSD-3-Clause — Details →
1.0.0 20 Mar 2017 none BSD-3-Clause — Details →
0.6.4 09 Feb 2017 none BSD-3-Clause — Details →
0.6.3 27 Dec 2016 none BSD-3-Clause — Details →
0.6.2 02 Dec 2016 none BSD-3-Clause — Details →
0.6.1 22 Nov 2016 none BSD-3-Clause — Details →
0.6.0 17 Nov 2016 none BSD-3-Clause — Details →
0.5.3 02 Nov 2016 none BSD-3-Clause — Details →
0.5.2 12 Oct 2016 none BSD-3-Clause — Details →
0.5.1 17 Aug 2016 none BSD-3-Clause — Details →
0.5.0 22 Jun 2016 none BSD-3-Clause — Details →
0.4.4 26 Apr 2016 none BSD-3-Clause — Details →
0.4.3 26 Apr 2016 none BSD-3-Clause — Details →
0.4.2 31 Mar 2016 none BSD-3-Clause — Details →
0.4.1 30 Mar 2016 none BSD-3-Clause — Details →
0.4.0 24 Mar 2016 none BSD-3-Clause — Details →
0.3.0 24 Feb 2016 none BSD-3-Clause — Details →
0.2.9 18 Feb 2016 none BSD-3-Clause — Details →
0.2.8 18 Feb 2016 none BSD-3-Clause — Details →
0.2.7 04 Feb 2016 none BSD-3-Clause — Details →
0.2.6 25 Jan 2016 none BSD-3-Clause — Details →
0.2.5 05 Nov 2015 none BSD-3-Clause — Details →
0.2.4 04 Nov 2015 none BSD-3-Clause — Details →
0.2.3 04 Nov 2015 none BSD-3-Clause — Details →
0.2.2 28 Oct 2015 none BSD-3-Clause — Details →
0.2.1 27 Oct 2015 none BSD-3-Clause — Details →
0.2.0 21 Oct 2015 none BSD-3-Clause — Details →
0.1.21 06 Oct 2015 none non-standard — Details →
0.1.20 17 Sep 2015 none non-standard — Details →
0.1.19 11 Sep 2015 none non-standard — Details →
0.1.18 10 Sep 2015 none non-standard — Details →
0.1.17 25 Aug 2015 none non-standard — Details →
0.1.16 24 Aug 2015 none non-standard — Details →
0.1.15 13 Aug 2015 none non-standard — Details →
0.1.14 13 Aug 2015 none non-standard — Details →
0.1.13 13 Aug 2015 none non-standard — Details →
0.1.12 13 Aug 2015 none non-standard — Details →
0.1.11 08 Jul 2015 none non-standard — Details →
0.1.10 24 Jun 2015 none non-standard — Details →
0.1.9 23 Jun 2015 none non-standard — Details →
0.1.8 22 Jun 2015 none non-standard — Details →
0.1.7 26 May 2015 none non-standard — Details →
0.1.6 26 May 2015 none non-standard — Details →
0.1.4 24 Apr 2015 none non-standard — Details →
0.1.3 24 Apr 2015 none non-standard — Details →
0.1.2 30 Mar 2015 none non-standard — Details →
0.1.1 11 Mar 2015 none non-standard — Details →
0.1.0 26 Feb 2015 none non-standard — Details →

All 90 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-mentions

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-mentions

Is react-mentions safe to use?

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

Vulert scores react-mentions 45/100, which reads as risky. 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). The registry marks the latest release as deprecated, which caps this score.

Is the latest version of react-mentions affected?

No. 4.4.10, 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-mentions should I use?

4.4.10 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-mentions have?

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

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

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