React meta-frameworks: star history compared
Picking React is the easy part; picking how to ship it is where teams argue. Next.js has pulled far ahead on stars, but the shape of each curve matters more than the totals: Gatsby's plateau marks the end of the static-site-only era, React Router's steady line reflects a decade as the default routing layer, and Expo's climb tracks React Native going mainstream. Compare the trajectories before you commit a codebase to one.
Ranked by current GitHub stars · growth = stars gained in the trailing 90 days · data updated Aug 2026
- vercel/next.js
- remix-run/react-router
- gatsbyjs/gatsby
- expo/expo
- redwoodjs/redwood
Ranking
5 repositories
| # | Repository | Stars | +90d | First star | Health |
|---|---|---|---|---|---|
| 1 | vercel/next.js | 141,210 | ~121 | 2016 | debt charts |
| 2 | remix-run/react-router | 56,537 | ~15 | 2014 | debt charts |
| 3 | gatsbyjs/gatsby | 55,937 | ~40 | 2015 | debt charts |
| 4 | expo/expo | 51,174 | ~124 | 2016 | debt charts |
| 5 | redwoodjs/redwood | 17,612 | ~6 | 2019 | debt charts |
Decision matrix
Repository health compared
Live Postgres analysis · unavailable data stays labeled
Popularity is only one axis. Compare technical scale, maintenance cadence, ownership resilience, and change pressure using the same completed repository analysis behind each report.
:: Reach
Popularity and real-world adoption
| Signal | vercel/next.js | remix-run/react-router | gatsbyjs/gatsby | expo/expo | redwoodjs/redwood |
|---|---|---|---|---|---|
| GitHub starsCurrent public GitHub metadata total. | ◆141,210 | 56,537 | 55,937 | 51,174 | 17,612 |
| Stars gained · trailing 90dChange in the newest 90 days covered by each cached series. | +121 | +15 | +40 | ◆+124 | +6 |
| ForksCurrent public GitHub metadata total. | Not available | Not available | Not available | Not available | Not available |
| Largest package audienceLargest resolved registry total; sources are shown explicitly. | No resolved package | No resolved package | No resolved package | No resolved package | No resolved package |
| Repository ageElapsed years since the GitHub creation timestamp. | 9.8 years | 12 years | 11 years | 10.0 years | 7.1 years |
:: Codebase
Size and technical center of gravity
| Signal | vercel/next.js | remix-run/react-router | gatsbyjs/gatsby | expo/expo | redwoodjs/redwood |
|---|---|---|---|---|---|
| Dominant languageLargest share of analyzed code lines at current HEAD. | Not available | Not available | Not available | Not available | Not available |
| Code linesAnalyzed source lines at current HEAD, excluding blanks and comments. | Not available | Not available | Not available | Not available | Not available |
| Languages representedLanguages with non-zero files or line counts. | Not available | Not available | Not available | Not available | Not available |
:: Maintenance
Commit volume and recent operating cadence
| Signal | vercel/next.js | remix-run/react-router | gatsbyjs/gatsby | expo/expo | redwoodjs/redwood |
|---|---|---|---|---|---|
| Repository commitsFull repository commit total reported by the analysis. | Not available | Not available | Not available | Not available | Not available |
| Commits · trailing 90dCommit count in the newest 90 days covered by the repository analysis. | Not available | Not available | Not available | Not available | Not available |
:: Ownership
How broadly maintenance responsibility is distributed
| Signal | vercel/next.js | remix-run/react-router | gatsbyjs/gatsby | expo/expo | redwoodjs/redwood |
|---|---|---|---|---|---|
| Bus factorFewest analyzed contributors carrying at least half the commits. | Not available | Not available | Not available | Not available | Not available |
| Top contributor concentrationShare of attributed commits carried by the most active contributor. | Not available | Not available | Not available | Not available | Not available |
:: Change signals
Debt markers and fix pressure in frequently changed files
| Signal | vercel/next.js | remix-run/react-router | gatsbyjs/gatsby | expo/expo | redwoodjs/redwood |
|---|---|---|---|---|---|
| Fix-labelled share · frequently changed filesFix-labelled commits divided by commits across the analyzed high-frequency file set. | Not available | Not available | Not available | Not available | Not available |
| Recent TODO/FIXME movementLatest cumulative marker count and its change over the trailing 90 days. | Not available | Not available | Not available | Not available | Not available |
Head to head
open in the builderFrequently asked
Which of these react meta-frameworks has the most GitHub stars?
vercel/next.js is the most-starred of the react meta-frameworks gitdebt compares, with 141,210 GitHub stars as of Aug 2026. It earned its first star in 2016.
Which of these react meta-frameworks is growing the fastest?
expo/expo added the most stars over the last 90 days of its cached history — about 124 new stars, compared with about 121 for the category leader vercel/next.js. 90-day figures are approximate for older repos, whose history is downsampled.
How is this comparison computed?
The table ranks public repository metadata by current total stars. When historical stargazer timestamps are available, gitdebt plots their cumulative series on shared axes and estimates trailing 90-day growth. Repo-health charts come independently from each repository's commit history.
Related categories
all categories- Static site generatorsAstro, Hugo, Eleventy, Jekyll, Zola and Hexo growth compared.6
- Frontend frameworksReact, Vue, Svelte, Angular, Solid and Preact head to head.6
- CSS frameworksTailwind CSS, Bootstrap, Bulma, UnoCSS and Pico compared.5
- Open-source game enginesGodot, Bevy, libGDX, Defold and O3DE star history.5