Skip to content
gitdebt

gatsbyjs/gatsby vs vercel/next.js

  • gatsbyjs/gatsby

    Stars

    55,941

    First recorded star in 2015.

  • vercel/next.js

    Stars

    142,321

    First recorded star in 2016.

Star history overlay
152k STARS11 YR 4 MOgatsbyjs/gatsby64kvercel/next.js152k

gatsbyjs/gatsby: 63,595 stars on September 5, 2026. vercel/next.js: 151,739 stars on September 16, 2026.

Star history for gatsbyjs/gatsby
DateStars
May 22, 20151
September 21, 2015160
November 9, 20151779
December 27, 20151992
February 15, 20162192
April 2, 20162617
May 18, 20162887
July 5, 20163166
August 21, 20164721
October 6, 20165336
December 1, 20166761
January 17, 20177444
March 4, 20178468
April 20, 20179280
June 6, 201710171
July 22, 201712514
September 7, 201713593
October 24, 201715142
December 9, 201716507
January 25, 201819023
March 12, 201820672
April 29, 201822266
June 15, 201823517
July 31, 201825007
September 16, 201826538
November 2, 201828277
December 18, 201829865
February 3, 201931829
March 21, 201933859
May 7, 201935576
July 2, 201937363
August 18, 201938810
October 3, 201940327
November 19, 201941930
January 5, 202043113
February 20, 202044524
April 7, 202045737
May 23, 202047161
July 9, 202048414
August 26, 202049552
October 11, 202050561
November 27, 202051357
January 13, 202152184
February 28, 202152942
April 16, 202153669
June 5, 202154409
July 22, 202154987
September 10, 202155490
November 3, 202155854
December 20, 202156333
February 14, 202256980
April 2, 202257412
May 18, 202257823
July 4, 202258253
August 19, 202258587
October 5, 202258923
November 21, 202259234
January 6, 202359490
February 22, 202359805
April 10, 202360087
May 26, 202360359
July 12, 202360593
August 27, 202360816
October 14, 202360976
November 30, 202361127
January 15, 202461308
March 3, 202461470
April 20, 202461628
June 6, 202461822
July 23, 202462000
September 18, 202462175
November 3, 202462367
December 25, 202462501
February 10, 202562974
April 1, 202563157
May 20, 202563298
July 20, 202563385
September 22, 202563466
January 7, 202663530
September 5, 202663595
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

Signalgatsbyjs/gatsbyvercel/next.js
GitHub starsCurrent public GitHub metadata total.55,941Best result in this row: 142,321
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.11 years9.9 years

Codebase

Size and technical center of gravity

Signalgatsbyjs/gatsbyvercel/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

Signalgatsbyjs/gatsbyvercel/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

Signalgatsbyjs/gatsbyvercel/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

Signalgatsbyjs/gatsbyvercel/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 gatsbyjs/gatsby and vercel/next.js were read
Fieldgatsbyjs/gatsbyvercel/next.js
SourceHistorical star dataHistorical star data
CoverageCovers through September 5, 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, gatsbyjs/gatsby or vercel/next.js?

    GitHub reports 142,321 stars for vercel/next.js and 55,941 for gatsbyjs/gatsby.

  • Do both star histories cover the same period?

    Not necessarily, and each chart names its own. gatsbyjs/gatsby — Historical star data · Covers through September 5, 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.