Skip to content
gitdebt

hashicorp/nomad vs k3s-io/k3s

  • hashicorp/nomad

    Stars

    16,954

    First recorded star in 2015.

  • k3s-io/k3s

    Stars

    33,970

    First recorded star in 2018.

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

hashicorp/nomad: 17,110 stars on September 16, 2026. k3s-io/k3s: 32,438 stars on September 16, 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 28, 20172900
October 14, 20173049
November 30, 20173235
January 16, 20183361
March 6, 20183524
April 22, 20183644
June 7, 20183793
July 24, 20183920
September 13, 20184067
November 1, 20184189
December 17, 20184341
February 5, 20194481
March 25, 20194731
May 9, 20195000
June 24, 20195144
August 10, 20195361
October 3, 20195603
November 20, 20195758
January 7, 20205954
February 21, 20206172
April 8, 20206373
May 25, 20206587
July 9, 20206909
August 27, 20207090
October 12, 20207398
November 26, 20207648
January 9, 20218164
February 25, 20218739
April 12, 20218975
May 30, 20219173
July 15, 20219397
August 31, 20219608
October 17, 202110769
December 9, 202110995
January 24, 202211227
March 10, 202211450
May 2, 202211727
June 17, 202211945
August 2, 202212784
September 16, 202213003
November 1, 202213526
December 16, 202213717
January 30, 202313948
March 18, 202314141
May 3, 202314350
June 19, 202314508
August 3, 202314671
September 20, 202314826
November 5, 202314974
December 25, 202315096
February 11, 202415213
March 31, 202415337
May 17, 202415485
July 10, 202415610
August 24, 202415773
October 10, 202415915
December 4, 202416110
January 23, 202516250
March 11, 202516446
May 4, 202516565
June 27, 202516686
August 21, 202516785
October 21, 202516882
January 3, 202616979
March 8, 202617046
September 16, 202617110
Star history for k3s-io/k3s
DateStars
September 22, 20183
November 24, 2018521
January 18, 2019610
February 24, 2019976
March 30, 20195962
May 3, 20196732
June 6, 20197399
July 10, 20197912
August 13, 20198405
September 16, 20198952
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 2, 202014839
November 5, 202015240
December 9, 202015738
January 12, 202116161
February 15, 202116493
March 21, 202116848
April 24, 202117208
June 1, 202117576
July 5, 202117858
August 8, 202118219
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 2, 202221656
October 6, 202221955
November 9, 202222248
December 13, 202222538
January 16, 202322816
February 19, 202323182
March 25, 202323456
April 28, 202323781
June 1, 202324086
July 5, 202324344
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 22, 202428198
August 25, 202428531
September 28, 202428911
November 1, 202429200
December 5, 202429474
January 8, 202529752
February 11, 202530020
March 17, 202530314
April 20, 202530651
May 24, 202531007
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 16, 202632438
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,954Best result in this row: 33,970
Stars gained · trailing 90dChange in the newest 90 days covered by each cached series.+15Best result in this row: +28
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 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, hashicorp/nomad or k3s-io/k3s?

    GitHub reports 33,970 stars for k3s-io/k3s and 16,954 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 16, 2026 · Still updating. k3s-io/k3s — 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.