Is react healthy, maintained, and safe?
Mostly yes — react is maintained, with a couple of watch-items rather than red flags.
The verdict
react earns a health score of 72/100, a low risk rating, computed deterministically from live npm release history, maintainer data, and the OSV vulnerability database. Mostly yes — react is maintained, with a couple of watch-items rather than red flags.
Its most recent release shipped on 23 July 2026 — 4 days ago — so development is clearly active. Across 2884 releases the cadence has been steady, which is a good sign of an ongoing maintenance rhythm. Two maintainers are listed; better than a lone author, but still a thin bench if one steps away.
OSV lists 2 known advisories for react, including 1 high. Review whether your version is in the affected range and whether a fixed release is available before depending on it. Each advisory is listed with its OSV/GHSA identifier below.
A couple of watch-items aside, react is a reasonable dependency to rely on; keep an eye on the flagged signals. This is a one-time snapshot of a single package — real projects depend on dozens or hundreds of packages, and any one of them can drift or be compromised between releases. Run your own package.json through the free health check, or have OSPulse monitor your whole dependency tree continuously.
Evidence trail — deterministic, auditable
Known vulnerabilities (2)
Cross-Site Scripting in react
Cross-Site Scripting in react
Key facts
- Latest version
- v19.2.8
- Last release
- 23 July 2026 (4 days ago)
- Total releases
- 2884
- First release
- 26 October 2011
- Package age
- 14.8 years
- Maintainers
- 2
- Known advisories
- 2
- Confidence
- High
Frequently asked
Is react still maintained?
Yes — react released as recently as 23 July 2026 (4 days ago), so it is actively maintained.
Does react have known security vulnerabilities?
Yes — OSV lists 2 advisories for react. See the advisory list on this page for the OSV/GHSA identifiers.
Is react safe to use?
Mostly yes — react is maintained, with a couple of watch-items rather than red flags. OSPulse rates it 72/100 (low risk) based on release recency, cadence, maintainer bus factor and known vulnerabilities.
Other npm packages we've checked
react is one package. What about the other hundreds in your tree?
Paste your own package.json into the free health check for an instant snapshot — or let OSPulse monitor your whole dependency tree continuously, before your CVE scanner wakes up.
Data from the npm registry & OSV.dev · snapshot generated 2026-07-27 · scores are deterministic and recomputed on each refresh.
