Skip to content
gitdebt

hashicorp/nomad vs k3s-io/k3s

  • hashicorp/nomad

    Stars

    16,951

    First recorded star in 2015.

  • k3s-io/k3s

    Stars

    33,960

    First recorded star in 2018.

Star history overlay
32k STARS11 YRhashicorp/nomad17kk3s-io/k3s32k

hashicorp/nomad: 17,109 stars on September 15, 2026. k3s-io/k3s: 32,437 stars on September 15, 2026.

Star history for hashicorp/nomad
DateStars
September 28, 2015228
November 11, 20151083
December 30, 20151216
February 16, 20161344
April 7, 20161511
May 22, 20161641
July 16, 20161774
September 7, 20161902
October 31, 20162031
December 18, 20162170
February 18, 20172316
April 9, 20172470
May 27, 20172600
July 14, 20172732
August 27, 20172896
October 14, 20173049
November 30, 20173235
January 16, 20183361
March 6, 20183524
April 21, 20183643
June 7, 20183793
July 24, 20183920
September 13, 20184067
November 1, 20184189
December 16, 20184337
February 5, 20194481
March 25, 20194731
May 9, 20195000
June 23, 20195137
August 9, 20195352
October 3, 20195603
November 20, 20195758
January 7, 20205954
February 20, 20206165
April 7, 20206364
May 25, 20206587
July 9, 20206909
August 27, 20207090
October 11, 20207388
November 25, 20207646
January 9, 20218164
February 25, 20218739
April 11, 20218969
May 29, 20219172
July 14, 20219393
August 31, 20219608
October 17, 202110769
December 8, 202110988
January 23, 202211217
March 9, 202211441
May 2, 202211727
June 17, 202211945
August 1, 202212777
September 15, 202212997
October 31, 202213520
December 16, 202213717
January 29, 202313944
March 17, 202314136
May 2, 202314346
June 18, 202314506
August 3, 202314671
September 19, 202314822
November 4, 202314967
December 23, 202315095
February 10, 202415210
March 31, 202415337
May 16, 202415481
July 9, 202415607
August 23, 202415772
October 9, 202415913
December 2, 202416107
January 22, 202516248
March 10, 202516444
May 3, 202516559
June 26, 202516685
August 19, 202516781
October 19, 202516881
January 2, 202616975
March 7, 202617044
September 15, 202617109
Star history for k3s-io/k3s
DateStars
September 22, 20183
November 22, 2018520
January 17, 2019608
February 23, 2019971
March 29, 20195937
May 2, 20196713
June 5, 20197386
July 9, 20197899
August 12, 20198388
September 15, 20198938
October 26, 20199500
November 29, 201910733
January 2, 202011293
February 5, 202011770
March 10, 202012179
April 13, 202012656
May 17, 202013163
June 20, 202013574
July 24, 202013937
August 28, 202014374
October 1, 202014834
November 4, 202015219
December 8, 202015713
January 11, 202116146
February 14, 202116486
March 20, 202116837
April 23, 202117198
May 31, 202117569
July 4, 202117852
August 7, 202118210
September 20, 202118597
October 30, 202118799
December 3, 202119123
January 6, 202219456
February 9, 202219851
March 15, 202220139
April 18, 202220465
May 22, 202220788
June 25, 202221047
July 29, 202221333
September 1, 202221649
October 5, 202221944
November 8, 202222237
December 12, 202222529
January 15, 202322802
February 18, 202323176
March 24, 202323448
April 27, 202323772
May 31, 202324079
July 4, 202324334
August 15, 202325015
September 18, 202325338
October 22, 202325640
November 25, 202325971
December 29, 202326310
February 1, 202426641
March 6, 202427016
April 9, 202427323
May 14, 202427623
June 17, 202427886
July 21, 202428184
August 24, 202428525
September 27, 202428905
October 31, 202429193
December 4, 202429462
January 7, 202529737
February 10, 202530011
March 16, 202530306
April 19, 202530646
May 23, 202531002
July 3, 202531252
August 7, 202531439
September 10, 202531623
October 21, 202531787
November 25, 202531927
December 29, 202532096
February 2, 202632208
March 15, 202632322
May 3, 202632391
September 15, 202632437
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

Signalhashicorp/nomadk3s-io/k3s
GitHub starsCurrent public GitHub metadata total.16,951Best result in this row: 33,960
Stars gained · trailing 90dChange in the newest 90 days covered by each cached series.+16Best result in this row: +19
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 years8.3 years

Codebase

Size and technical center of gravity

Signalhashicorp/nomadk3s-io/k3s
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

Signalhashicorp/nomadk3s-io/k3s
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

Signalhashicorp/nomadk3s-io/k3s
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

Signalhashicorp/nomadk3s-io/k3s
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 hashicorp/nomad and k3s-io/k3s were read
Fieldhashicorp/nomadk3s-io/k3s
SourceHistorical star dataHistorical star data
CoverageCovers through September 15, 2026Covers through September 15, 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, hashicorp/nomad or k3s-io/k3s?

    GitHub reports 33,960 stars for k3s-io/k3s and 16,951 for hashicorp/nomad.

  • Do both star histories cover the same period?

    Not necessarily, and each chart names its own. hashicorp/nomad — Historical star data · Covers through September 15, 2026 · Still updating. k3s-io/k3s — Historical star data · Covers through September 15, 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.