Skip to report

Independent analytics for a public GitHub repository

facebook/react

The library for web and native user interfaces. — view on GitHub · react.dev

Language

JavaScript

License

MIT

open source

Created

May 2013

Stars

250,635

Forks

51,388

Issues

858 open

Updated 21 Sept 2026, 21:29 UTC

95 /100
ACTIVELY MAINTAINED

tracker score 95/100 methodology →

Computed from release cadence, responsiveness, backlog trend and contributor depth.

Last release

12 days ago

v19.3.0

Cadence

bursty, <1d median

12d gap

PR merge median

1.5d

Issue response median

24.8h

Commits / 7d

17

1273 points on Hacker News — “Shopify is moving from React Native back to Swift and Kotlin” source →

Attention vs delivery — is popularity translating into shipping?

The signature question of dependency due diligence. Columns: commits per month (activity). Line: merged pull requests per month (delivery). 12 full months.

attention — commits / month delivery — merged PRs / month stable release

Reading: delivery held at ~1 merged PRs/mo over the last 12 months. No divergence risk — delivery tracks attention.

Star-spike forensics — why did this repo blow up, and when?

Star-velocity anomalies cross-referenced with Hacker News, Reddit and release events.

986 points on Hacker News — “ChatGPT won't let you type until Cloudflare reads your React state” source →

628 points on Hacker News — “RCE Vulnerability in React and Next.js” source →

346 points on Hacker News — “Denial of service and source code exposure in React Server Components” source →

Responsiveness — vs cohort percentiles

How fast maintainers answer, review and merge — ranked against repos of similar size and age.

Issue first non-author response

median 24.8hcohort: n/a

PR first review

median 11.4hcohort: n/a

PR merge time

median 1.5dcohort: n/a

Bots excluded Sample: 30 merged PRs (90d) / 14 recent issues. Percentile position measured from the left — shorter is faster.

First-contributor funnel — what happens to a newcomer’s PR?

0

first-time PRs (12 mo)

—

got a response

n=0 scanned

—

were merged

0 newcomer candidates

—

returned ≤90d

verified via author history

Verdict: not enough first-time PRs in the sampled window (2026-03-25..2026-06-23) to call this either way — most contributions here come from people already close to the project.

Contributor concentration (12 mo)

top 1 — 21.5% of accepted changes · last commit Sep 13

top 3 — 45.8% of accepted changes

long tail — 44 further authors

Verdict: low key-person risk. 47 human commit authors in 12 months; top author (eps1lon) holds 21.5%, top 3 hold 45.8%, 15 authors above 1% each.

Open-issue backlog

Open issues and pull requests right now. Trend history builds from daily tracking.

open issues & PRs — right now

858

open issues

517

open pull requests

Tracking daily since 25 Aug 2026 — 21 snapshots so far. Score moved 86 → 95 over the past 27d.

1,375 open

858 issues + 517 PRs · backlog up 8% over 27d

Fork network & successors

51,388 forks · 0 with independent momentum

zilverline/react-tap-event-plugin — 1,052★ · last push 3037d ago

stale

facebook/react is upstream — no successor needed (project active). Top forks by stars are all stale (pushes >1y ago). Successor detection activates if the repo goes dormant.

If this repo goes dormant, this section becomes “Where did development continue?” — with evidence labels per fork.

What changed — last 90d

4 stable releases in 90d (median gap 0.0d)

Issue response sits at a 24.8h median — up from 5.9h 27d ago

License unchanged · not archived · no rename/transfer

Max release gap in 12mo: 72d (cadence 0.0d median)

Frequently asked answered from live data · FAQPage structured data

These answers regenerate on every snapshot — they never rot.

Is react still maintained?

Yes — actively (score 95/100). Last stable release v19.3.0 12 days ago, 17 commits in the last full week, median PR merge 1.5d. Evidence collected Mon Sep 21 2026.

What license does react use?

MIT — as reported by GitHub.

When was the last react release?

v19.3.0, 12 days ago. Median gap between stable releases is 0.0 days; 4 stable releases shipped in the last 90 days — the current 12d gap is well above that median.

Is react safe to adopt for a new project in 2026?

On the evidence: yes. 47 human authors in 12 months, no fork-succession pressure. Not published to npm — GitHub activity only.

Share & embed — every share is a branded mini-report

Link preview (auto-generated OG card)

tracker.git.tools

facebook/react

ACTIVELY MAINTAINED · 95/100

ships bursty, <1d median · PR merge 1.5d · ★ 250,635

facebook/react — maintenance verdict & repo intelligence · tracker.git.tools

README badge (live SVG — every embed is a backlink)

maintenance active · 95
[![maintenance](https://tracker.git.tools/badge/facebook/react)](https://tracker.git.tools/facebook/react)

Badge states: active · slowing · maintenance-only · dormant — flips automatically; maintainers embed it because it’s honest.

Methodology

Built from the public GitHub API, the npm registry, deps.dev and Hacker News. Known bot accounts are excluded from response and merge metrics. Verdicts are computed from the evidence shown on this page — nothing is scored that you cannot see. Reports refresh daily.