Vulnerability Database · npm · Package report

better-react-mathjax: vulnerability history, versions and safety

better-react-mathjax 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.

Vulert verdict on better-react-mathjax 3.0.3 i

Updated on 23 Oct 2026

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

Package health score 69/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Inactive

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

  • Current release 3.0.3 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 3 packages i
  • Stars 188 i
  • OpenSSF scorecard 1/10 i
  • Last release this month 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 better-react-mathjax, 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
3.0.3 14 Oct 2026 none MIT — Details →
3.0.3-beta 18 Sep 2026 none MIT — Details →
3.0.2 28 Aug 2026 none MIT — Details →
3.0.1 26 Apr 2026 none MIT — Details →
3.0.0 11 Feb 2026 none MIT — Details →
2.4.0-beta-1 18 Nov 2025 none MIT — Details →
2.3.0 15 Apr 2025 none MIT — Details →
2.2.0 11 Apr 2025 none MIT — Details →
2.1.0 30 Jan 2025 none MIT — Details →
2.0.4-beta1 11 Nov 2024 none MIT — Details →
2.0.3 07 Oct 2023 none MIT — Details →
2.0.2 07 Aug 2022 none MIT — Details →
2.0.1 23 Apr 2022 none MIT — Details →
2.0.0 26 Mar 2022 none MIT — Details →
1.0.3 30 Aug 2021 none MIT — Details →
1.0.2 22 Apr 2021 none MIT — Details →
1.0.1 05 Apr 2021 none MIT — Details →
1.0.0-alpha.1 05 Apr 2021 none MIT — Details →
1.0.0 02 Apr 2021 none MIT — Details →
0.0.32-beta 02 Apr 2021 none MIT — Details →
0.0.30-beta 01 Apr 2021 none MIT — Details →
0.0.28-beta 31 Mar 2021 none MIT — Details →
0.0.25-beta 30 Mar 2021 none MIT — Details →
0.0.24-beta 30 Mar 2021 none MIT — Details →
0.0.23-beta 27 Mar 2021 none MIT — Details →
0.0.20-beta 24 Mar 2021 none MIT — Details →
0.0.18-beta 20 Mar 2021 none MIT — Details →
0.0.17-beta 18 Mar 2021 none MIT — Details →
0.0.14-beta 17 Feb 2021 none MIT — Details →
0.0.13-beta 17 Feb 2021 none MIT — Details →
0.0.11-beta 14 Feb 2021 none MIT — Details →
0.0.10-beta 13 Feb 2021 none MIT — Details →

All 32 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 better-react-mathjax

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 better-react-mathjax

Is better-react-mathjax safe to use?

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

Vulert scores better-react-mathjax 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 better-react-mathjax affected?

No. 3.0.3, 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.

How many vulnerabilities does better-react-mathjax have?

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

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

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