Discofork
Repository brief

facebook/react

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis
cached 2026-03-29T21:56:58.898Z
3mo ago

facebook/react

facebook/react is the main React repository: a very large, actively maintained JavaScript library for building web and native user interfaces. It has very high adoption signals (244,258 stars, 50,872 forks) and very recent activity, including commits from 2026-03-29. Forks are likely interesting if you care about UI frameworks, rendering/runtime internals, or tooling around React itself.

GitHub
Loading tags...
Stars244,258
Forks50,872
Default branchmain
Last pushed2026-03-29T01:18:21Z
Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

6 of 6 fork briefs
Selected

Prefer this fork only if you have a legacy React app that specifically needs its tap-event behavior and you can tolerate a stale, deprecated codebase. If you want current React capabilities or long-term maintenance, upstream is the safer choice.

Prefer this fork only if your goal is specifically the fork's Suspense/server-rendering experiment. For most users, upstream React is the better choice because this fork is stale, heavily diverged, and missing years of upstream fixes and features.

Choose this fork only if you explicitly need a legacy, highly customized React tree with extra maintenance tooling. If you want current React capabilities or low-risk adoption, upstream is the better choice.

Prefer this fork only if you need an older, heavily customized React baseline and are willing to own long-term divergence. If you want current React behavior, tooling, or compatibility, upstream is the better choice.

Prefer this fork only if you need its older customized React snapshot or internal experimentation work. For normal application or library use, upstream React is the better choice because this fork is stale and materially behind current fixes and features.

Choose this fork only if legacy browser support is the primary requirement. For almost everyone else, upstream React is the better choice because this fork is frozen, heavily diverged, and missing years of maintenance and feature work.