Skip to content
gitdebt

docker/compose vs k3s-io/k3s

  • docker/compose

    Stars

    38,165

    First recorded star in 2013.

  • k3s-io/k3s

    Stars

    33,960

    First recorded star in 2018.

Star history overlay
40k STARS12 YR 9 MOdocker/compose40kk3s-io/k3s32k

docker/compose: 39,975 stars on September 14, 2026. k3s-io/k3s: 32,437 stars on September 15, 2026.

Star history for docker/compose
DateStars
December 10, 20132
February 21, 2014806
April 18, 20141936
June 19, 20142162
August 15, 20142725
October 10, 20143309
December 5, 20144110
January 30, 20154762
March 27, 20155563
May 22, 20156010
July 28, 20156455
September 22, 20156779
November 17, 20157106
January 13, 20167414
March 9, 20167768
May 4, 20168123
June 29, 20168397
August 24, 20168765
October 19, 20169081
December 15, 20169382
February 10, 20179757
April 7, 201710172
June 2, 201710586
July 28, 201711036
September 22, 201711465
November 17, 201712000
January 12, 201812586
March 9, 201813165
May 6, 201813728
July 2, 201814231
September 7, 201814814
November 2, 201815440
December 28, 201815969
February 22, 201916511
April 19, 201917168
June 14, 201917782
August 9, 201918448
October 4, 201919018
November 29, 201919616
January 24, 202020137
March 20, 202020736
May 15, 202021353
July 10, 202021964
September 6, 202022503
November 1, 202022988
December 27, 202023495
February 21, 202124017
April 19, 202124555
June 17, 202124975
August 12, 202125405
October 24, 202126071
December 24, 202126667
February 18, 202227220
April 15, 202227789
June 10, 202228532
August 5, 202229121
September 30, 202229729
November 25, 202230255
January 20, 202330776
March 17, 202331383
May 12, 202331985
July 7, 202332517
September 1, 202333032
October 27, 202333496
December 22, 202334012
February 16, 202434700
April 12, 202435181
June 7, 202435700
August 2, 202436303
September 27, 202436865
December 3, 202437438
January 28, 202537914
March 25, 202538429
May 20, 202538861
July 16, 202539137
September 11, 202539382
November 13, 202539591
January 15, 202639749
March 28, 202639889
September 14, 202639975
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

Signaldocker/composek3s-io/k3s
GitHub starsCurrent public GitHub metadata total.Best result in this row: 38,16533,960
Stars gained · trailing 90dChange in the newest 90 days covered by each cached series.Best result in this row: +28+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.13 years8.3 years

Codebase

Size and technical center of gravity

Signaldocker/composek3s-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

Signaldocker/composek3s-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

Signaldocker/composek3s-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

Signaldocker/composek3s-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 docker/compose and k3s-io/k3s were read
Fielddocker/composek3s-io/k3s
SourceHistorical star dataHistorical star data
CoverageCovers through September 14, 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, docker/compose or k3s-io/k3s?

    GitHub reports 38,165 stars for docker/compose and 33,960 for k3s-io/k3s.

  • Do both star histories cover the same period?

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