Skip to content
gitdebt

hashicorp/nomad vs k3s-io/k3s

  • hashicorp/nomad

    Stars

    17,098

    First recorded star in 2015.

  • k3s-io/k3s

    Stars

    34,401

    First recorded star in 2018.

Star history overlay
34k STARS11 YR 5 MOhashicorp/nomad17kk3s-io/k3s34k

hashicorp/nomad: 17,098 stars on November 13, 2026. k3s-io/k3s: 34,401 stars on November 14, 2026.

Star history for hashicorp/nomad
DateStars
June 1, 20151
November 9, 2015921
January 5, 20161054
February 27, 20161183
April 19, 20161320
June 13, 20161451
August 15, 20161570
October 9, 20161699
December 3, 20161817
February 1, 20171939
April 7, 20172111
June 1, 20172234
July 22, 20172370
September 10, 20172514
October 30, 20172662
December 20, 20172817
February 9, 20182957
March 30, 20183096
May 19, 20183235
July 11, 20183379
August 29, 20183495
October 21, 20183632
December 11, 20183788
February 2, 20193945
March 24, 20194165
May 12, 20194412
July 1, 20194561
August 20, 20194774
October 10, 20194961
November 30, 20195125
January 27, 20205352
March 17, 20205524
May 6, 20205733
June 23, 20206023
August 12, 20206198
October 6, 20206474
November 24, 20206715
January 11, 20217172
March 1, 20217678
April 18, 20217893
June 4, 20218089
July 22, 20218309
September 9, 20218511
October 28, 20219595
December 15, 20219815
February 2, 202210036
March 23, 202210241
May 11, 202210512
June 28, 202211180
August 18, 202211572
October 15, 202212105
December 3, 202212353
January 22, 202312585
March 12, 202312780
April 29, 202313003
June 21, 202313169
August 11, 202313348
September 30, 202313506
November 17, 202313644
January 10, 202413771
March 1, 202413900
April 23, 202414045
June 17, 202414187
August 5, 202414335
September 24, 202414508
November 13, 202414663
January 1, 202514820
February 20, 202515016
April 15, 202515152
June 9, 202515291
August 10, 202515499
October 2, 202515656
November 24, 202515824
January 18, 202615977
March 9, 202616143
April 28, 202616365
June 18, 202616537
August 6, 202616730
September 25, 202616940
November 13, 202617098
Star history for k3s-io/k3s
DateStars
September 22, 20183
November 26, 2018525
January 25, 2019656
March 2, 20193471
April 8, 20195622
May 15, 20196340
June 20, 20196888
July 27, 20197403
September 1, 20197889
October 8, 20198351
November 21, 20199320
December 28, 201910146
February 2, 202010579
March 10, 202010993
April 15, 202011434
May 22, 202011927
June 28, 202012314
August 3, 202012671
September 9, 202013165
October 16, 202013545
November 21, 202014020
December 28, 202014442
February 2, 202114818
March 11, 202115155
April 17, 202115490
May 23, 202115901
June 29, 202116186
August 4, 202116522
September 10, 202116847
October 17, 202117191
November 30, 202117556
January 5, 202217862
February 11, 202218242
March 19, 202218538
April 25, 202218884
June 1, 202219216
July 7, 202219530
August 13, 202219824
September 19, 202220144
October 25, 202220452
December 1, 202220782
January 7, 202321043
February 13, 202321445
March 22, 202321742
April 27, 202322103
June 3, 202322430
July 10, 202322757
August 15, 202323366
September 21, 202323723
October 27, 202324053
December 10, 202324459
January 16, 202424832
February 22, 202425240
March 29, 202425559
May 5, 202425883
June 10, 202426158
July 17, 202426448
August 23, 202426774
September 28, 202427132
November 4, 202427440
December 10, 202427737
January 16, 202528030
February 22, 202528332
March 30, 202528662
May 6, 202529059
June 12, 202529456
July 18, 202529809
August 24, 202530165
September 29, 202530512
November 5, 202530837
December 19, 202531287
January 25, 202631644
March 2, 202632040
April 8, 202632435
May 14, 202632787
June 20, 202633128
July 27, 202633469
September 1, 202633776
October 8, 202634107
November 14, 202634401
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.17,098Best result in this row: 34,401
Stars gained · trailing 90dChange in the newest 90 days covered by each cached series.+368Best result in this row: +799
ForksCurrent public GitHub metadata total.Reading…Reading…
Largest package audienceLargest resolved registry total; sources are shown explicitly.Reading…Reading…
Repository ageElapsed years since the GitHub creation timestamp.11 years8.5 years

Codebase

Size and technical center of gravity

Signalhashicorp/nomadk3s-io/k3s
Dominant languageLargest share of analyzed code lines at current HEAD.Reading…Reading…
Code linesAnalyzed source lines at current HEAD, excluding blanks and comments.Reading…Reading…
Languages representedLanguages with non-zero files or line counts.Reading…Reading…

Maintenance

Commit volume and recent operating cadence

Signalhashicorp/nomadk3s-io/k3s
Repository commitsFull repository commit total reported by the analysis.Reading…Reading…
Commits · trailing 90dCommit count in the newest 90 days covered by the repository analysis.Reading…Reading…

Ownership

How broadly maintenance responsibility is distributed

Signalhashicorp/nomadk3s-io/k3s
Bus factorFewest analyzed contributors carrying at least half the commits.Reading…Reading…
Top contributor concentrationShare of attributed commits carried by the most active contributor.Reading…Reading…

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.Reading…Reading…
Recent TODO/FIXME movementLatest cumulative marker count and its change over the trailing 90 days.Reading…Reading…

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 always put them on one source: a series not yet read again from GitHub's star history can stop on the date GitHub closed its stargazer list, or be rebuilt from public archive events. Each column below states its own reading.

How the star series for hashicorp/nomad and k3s-io/k3s were read
Fieldhashicorp/nomadk3s-io/k3s
SourceGitHub star historyGitHub star history
CoverageCovers through November 14, 2026Covers through November 14, 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 34,401 stars for k3s-io/k3s and 17,098 for hashicorp/nomad.

  • Do both star histories cover the same period?

    Not necessarily, and each chart names its own. hashicorp/nomad — GitHub star history · Covers through November 14, 2026 · Still updating. k3s-io/k3s — GitHub star history · Covers through November 14, 2026 · Still updating. A series read from GitHub's star history runs to its latest read. One read before that existed can stop on the date GitHub closed its stargazer list in July 2026, or come from public archive events, until gitdebt reads it again.

  • 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.