Skip to content

denoland/deno vs nodejs/node

  • denoland/deno

    Stars

    108,454

    First recorded star in 2018.

  • nodejs/node

    Stars

    121,962

    First recorded star in 2014.

Star history overlay

135k STARS11 YR 10 MOdenoland/deno115knodejs/node135k

denoland/deno: 114,635 stars on September 16, 2026. nodejs/node: 135,357 stars on September 16, 2026.

Star history for denoland/deno
DateStars
May 29, 2018337
July 4, 201821093
August 10, 201822907
September 16, 201824454
October 23, 201825553
November 28, 201826483
January 4, 201927679
February 10, 201929588
March 19, 201930940
April 24, 201932665
June 8, 201934503
July 14, 201936058
August 20, 201937156
September 26, 201938075
November 2, 201938847
December 8, 201939681
January 14, 202040750
February 20, 202044803
March 28, 202046266
May 3, 202048183
June 9, 202063917
July 16, 202066739
August 23, 202068183
September 28, 202069443
November 4, 202070712
December 11, 202072424
January 17, 202173809
February 23, 202175416
March 31, 202176724
May 7, 202178274
June 23, 202179395
July 30, 202180233
September 8, 202181134
October 16, 202181764
November 26, 202182366
January 2, 202283115
February 8, 202284070
March 17, 202284934
April 22, 202286003
May 29, 202287021
July 5, 202288116
August 11, 202289035
September 16, 202290039
October 23, 202290845
November 29, 202291605
January 5, 202392227
February 10, 202393189
March 19, 202393961
April 25, 202394671
June 1, 202395424
July 15, 202396048
August 21, 202396592
September 26, 202397253
November 2, 202397832
December 9, 202398289
January 15, 202498767
February 21, 202499507
March 28, 2024100078
May 4, 2024100551
June 10, 2024101012
July 17, 2024101469
August 22, 2024101917
September 28, 2024102771
November 4, 2024105634
December 11, 2024106853
January 16, 2025109757
February 22, 2025110674
March 31, 2025111363
May 7, 2025111955
June 12, 2025112401
July 27, 2025112793
September 1, 2025113093
October 8, 2025113494
November 20, 2025113752
December 27, 2025113973
February 1, 2026114179
March 11, 2026114343
April 20, 2026114474
June 4, 2026114553
September 16, 2026114635
Star history for nodejs/node
DateStars
November 26, 20144
January 17, 20158517
March 11, 201511176
May 3, 201512321
June 25, 201513256
August 17, 201514069
October 9, 201516799
December 1, 201518882
January 24, 201620880
March 17, 201622777
May 19, 201625241
July 11, 201627091
September 2, 201628929
October 25, 201631039
December 17, 201633039
February 8, 201735753
April 2, 201738363
May 25, 201740473
July 16, 201742550
September 7, 201744800
October 30, 201747614
December 22, 201750217
February 13, 201852262
April 8, 201854307
May 31, 201856628
July 23, 201858785
September 14, 201860700
November 6, 201862584
December 28, 201864323
February 19, 201966045
April 24, 201968668
June 16, 201970655
August 8, 201972227
September 30, 201973631
November 22, 201975256
January 13, 202076757
March 6, 202078056
April 28, 202079858
June 20, 202081777
August 12, 202083296
October 5, 202084731
November 27, 202086678
January 19, 202188023
March 13, 202189839
May 5, 202191307
June 29, 202192865
August 21, 202194801
October 16, 202195989
December 13, 202197252
February 4, 202299225
April 9, 2022101081
June 1, 2022102515
July 23, 2022103719
September 14, 2022105295
November 6, 2022106563
December 29, 2022107743
February 20, 2023109113
April 14, 2023110526
June 6, 2023111990
July 29, 2023113246
September 20, 2023114617
November 12, 2023116503
January 3, 2024118400
February 25, 2024119753
April 18, 2024121776
June 10, 2024123184
August 2, 2024124643
September 24, 2024125872
November 16, 2024127260
January 8, 2025128501
March 12, 2025130120
May 4, 2025131210
June 26, 2025132123
August 18, 2025132878
October 15, 2025133501
December 8, 2025133976
January 30, 2026134460
March 24, 2026134797
May 18, 2026135005
September 16, 2026135357

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

Signaldenoland/denonodejs/node
GitHub starsCurrent public GitHub metadata total.108,454Best result in this row: 121,962
Stars gained · trailing 90dChange in the newest 90 days covered by each cached series.+70Best result in this row: +333
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.8.3 years12 years

Codebase

Size and technical center of gravity

Signaldenoland/denonodejs/node
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

Signaldenoland/denonodejs/node
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

Signaldenoland/denonodejs/node
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

Signaldenoland/denonodejs/node
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 denoland/deno and nodejs/node were read
Fielddenoland/denonodejs/node
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, denoland/deno or nodejs/node?

    GitHub reports 121,962 stars for nodejs/node and 108,454 for denoland/deno.

  • Do both star histories cover the same period?

    Not necessarily, and each chart names its own. denoland/deno — Historical star data · Covers through September 16, 2026 · Still updating. nodejs/node — 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.