Skip to content
gitdebt

remix-run/react-router vs vercel/next.js

  • remix-run/react-router

    Stars

    56,572

    First recorded star in 2014.

  • vercel/next.js

    Stars

    142,320

    First recorded star in 2016.

Star history overlay
152k STARS12 YR 4 MOremix-run/react-router63kvercel/next.js152k

remix-run/react-router: 62,777 stars on September 16, 2026. vercel/next.js: 151,739 stars on September 16, 2026.

Star history for remix-run/react-router
DateStars
May 17, 20142
July 19, 2014410
September 12, 2014825
November 5, 20141274
December 28, 20141845
February 20, 20152902
April 15, 20153908
June 7, 20154829
July 31, 20155797
September 23, 20157006
November 26, 20159029
January 20, 201610550
March 13, 201611918
May 6, 201613385
June 29, 201614733
August 21, 201616012
October 14, 201617764
December 7, 201619179
January 29, 201720392
March 24, 201722272
May 17, 201723804
July 9, 201725111
September 1, 201726523
October 25, 201727753
December 17, 201729070
February 9, 201830492
April 5, 201831717
May 28, 201832846
July 21, 201833965
September 13, 201834917
November 16, 201835989
January 9, 201936775
March 3, 201937646
April 26, 201938715
June 19, 201939549
August 11, 201940311
October 4, 201941030
November 27, 201941730
January 19, 202042270
March 13, 202043184
May 6, 202043979
June 29, 202044753
August 21, 202045380
October 15, 202045863
December 8, 202046311
January 30, 202146971
March 26, 202147398
May 22, 202147798
July 14, 202148221
September 9, 202148696
November 18, 202149502
January 11, 202250508
March 6, 202251217
April 28, 202251836
June 21, 202252442
August 14, 202252969
October 6, 202253645
November 29, 202254333
January 22, 202354895
March 16, 202355412
May 9, 202355890
July 2, 202356294
August 24, 202356683
October 17, 202356992
December 10, 202357330
February 1, 202457704
March 27, 202458019
May 20, 202458432
July 12, 202458970
September 4, 202459343
November 7, 202459820
December 31, 202460424
February 23, 202561001
April 17, 202561523
June 10, 202561963
August 4, 202562199
September 27, 202562392
November 30, 202562579
February 2, 202662690
September 16, 202662777
Star history for vercel/next.js
DateStars
October 25, 20161234
December 8, 20167134
January 21, 20178544
March 6, 20179603
April 19, 201712659
June 3, 201714466
July 17, 201715917
August 30, 201717401
October 13, 201718756
November 27, 201720332
January 19, 201822538
March 4, 201824157
April 18, 201825595
June 1, 201827031
July 15, 201828395
August 29, 201829692
October 12, 201831436
November 25, 201832914
January 8, 201934316
February 22, 201936136
April 7, 201937592
May 21, 201938958
July 4, 201940193
August 17, 201941868
October 1, 201943130
November 14, 201944436
December 28, 201945694
February 10, 202047231
March 26, 202048805
May 9, 202050725
July 1, 202053326
August 14, 202055344
September 28, 202057261
November 12, 202060802
December 26, 202063286
February 8, 202167149
March 24, 202169977
May 7, 202172075
June 24, 202176144
August 7, 202178323
September 23, 202180729
November 9, 202182453
December 24, 202185217
February 6, 202287980
March 22, 202290764
May 5, 202293932
June 18, 202296093
August 2, 202298536
September 15, 2022101035
October 29, 2022103827
December 21, 2022106852
February 3, 2023109442
March 20, 2023112125
May 3, 2023115041
June 16, 2023117715
July 30, 2023119785
September 13, 2023121909
October 27, 2023124566
December 10, 2023126623
January 23, 2024128520
March 7, 2024130658
April 21, 2024132593
June 4, 2024134310
July 18, 2024136004
August 31, 2024137530
October 15, 2024139214
November 28, 2024141487
January 11, 2025142891
February 24, 2025144388
April 9, 2025145906
June 1, 2025147382
July 16, 2025148298
August 29, 2025149078
October 17, 2025149736
November 30, 2025150193
January 14, 2026150775
February 27, 2026151156
April 12, 2026151451
May 31, 2026151589
September 16, 2026151739
add a third repository

Repository health compared

Live analysis · unavailable data stays labelled

Popularity is only one axis. Compare technical scale, maintenance cadence, ownership resilience and change pressure against the same completed analysis that sits behind each report.

Reach

Popularity and real-world adoption

Signalremix-run/react-routervercel/next.js
GitHub starsCurrent public GitHub metadata total.56,572Best result in this row: 142,320
Stars gained · trailing 90dChange in the newest 90 days covered by each cached series.+14Best result in this row: +133
ForksCurrent public GitHub metadata total.Not availableNot available
Largest package audienceLargest resolved registry total; sources are shown explicitly.No resolved packageNo resolved package
Repository ageElapsed years since the GitHub creation timestamp.12 years9.9 years

Codebase

Size and technical center of gravity

Signalremix-run/react-routervercel/next.js
Dominant languageLargest share of analyzed code lines at current HEAD.Not availableNot available
Code linesAnalyzed source lines at current HEAD, excluding blanks and comments.Not availableNot available
Languages representedLanguages with non-zero files or line counts.Not availableNot available

Maintenance

Commit volume and recent operating cadence

Signalremix-run/react-routervercel/next.js
Repository commitsFull repository commit total reported by the analysis.Not availableNot available
Commits · trailing 90dCommit count in the newest 90 days covered by the repository analysis.Not availableNot available

Ownership

How broadly maintenance responsibility is distributed

Signalremix-run/react-routervercel/next.js
Bus factorFewest analyzed contributors carrying at least half the commits.Not availableNot available
Top contributor concentrationShare of attributed commits carried by the most active contributor.Not availableNot available

Change signals

Debt markers and fix pressure in frequently changed files

Signalremix-run/react-routervercel/next.js
Fix-labelled share · frequently changed filesFix-labelled commits divided by commits across the analyzed high-frequency file set.Not availableNot available
Recent TODO/FIXME movementLatest cumulative marker count and its change over the trailing 90 days.Not availableNot available

Both curves are drawn on shared axes. They are not drawn from a shared source: each series names its own below.

One axis, two sources

The overlay puts both repositories on one axis. It does not put them on one source: since July 2026 a stargazer-list series stops on a fixed date, while a series rebuilt from public archive events keeps receiving points. Each column below states its own reading.

How the star series for remix-run/react-router and vercel/next.js were read
Fieldremix-run/react-routervercel/next.js
SourceHistorical star dataHistorical star data
CoverageCovers through September 16, 2026Covers through September 16, 2026
StateStill updatingStill updating

No row states how much of a history is missing. An archive series records star actions and not unstars, so it can exceed a repository's own star total, and a figure for the difference would be wrong exactly where it looks most precise.

Notes on this comparison

  • Which has more GitHub stars, remix-run/react-router or vercel/next.js?

    GitHub reports 142,320 stars for vercel/next.js and 56,572 for remix-run/react-router.

  • Do both star histories cover the same period?

    Not necessarily, and each chart names its own. remix-run/react-router — Historical star data · Covers through September 16, 2026 · Still updating. vercel/next.js — Historical star data · Covers through September 16, 2026 · Still updating. Since July 2026 GitHub serves a repository's stargazer list only to its own admins and collaborators, so one series can stop on a fixed date while the other keeps flowing from public archive events.

  • How is this comparison computed?

    Star totals come from public repository metadata. The two curves are each repository's stored star series drawn on shared axes, from whichever source is named above. Repository-health figures are computed independently from each project's commit history.