This page compares the source lines of code (SLOC) of kubernetes/kubernetes and docker/compose using cached OctoCounts reports. Code size is not code quality: a larger count only means more source material, not a better or worse project.
As of 2026-09-11, kubernetes/kubernetes contains 4,808,053 total lines (3,872,526 code) across 14,894 files, while docker/compose contains 65,805 total lines (48,128 code) across 532 files as of 2026-09-07. kubernetes/kubernetes is about 80x the size of docker/compose by code lines. Code size is not code quality: a larger count only means more source material, not a better or worse project.
| Metric | kubernetes/kubernetes | docker/compose |
|---|---|---|
| Files | 14,894 | 532 |
| Total lines | 4,808,053 | 65,805 |
| Code lines | 3,872,526 | 48,128 |
| Comment lines | 633,118 | 10,411 |
| Blank lines | 302,409 | 7,266 |
| Languages counted | 12 | 9 |
Top languages in kubernetes/kubernetes: Go (65.4% of code), JSON (26.7% of code), YAML (6.6% of code). Top languages in docker/compose: Go (95.3% of code), YAML (3.6% of code), Dockerfile (0.6% of code). Go, YAML appear in both top language lists; JSON, Shell, PO File appear only in kubernetes/kubernetes's top languages; Dockerfile, HCL, Makefile appear only in docker/compose's top languages.
Methodology: both counts come from cached OctoCounts reports generated with tokei. kubernetes/kubernetes was counted at ref a6d4708e816967a7d0c64155d6a702ab19463607 (commit a6d4708e8169) on 2026-09-11; docker/compose was counted at ref main (commit 7c808c29c3bb) on 2026-09-07. See the counting methodology for ignored directories and analysis options.
Evidence and next steps:
Note: code size is not code quality. OctoCounts only reports reproducible line counts and makes no claim that either project is better.
kubernetes/kubernetes has more code: 3,872,526 code lines versus 48,128 for docker/compose, about 80x as much, based on cached OctoCounts reports as of 2026-09-11.
Not necessarily. SLOC measures size, not complexity, quality, or maintainability. A larger codebase can mean more features, more generated or vendored code, more verbose language idioms, or more tests — none of which imply the code is harder to work with. Use SLOC to gauge the scale of what you'd be reading or maintaining, not as a quality signal for kubernetes/kubernetes, docker/compose, or any repository.
Methodology: both counts come from cached OctoCounts reports generated with tokei. kubernetes/kubernetes was counted at ref a6d4708e816967a7d0c64155d6a702ab19463607 (commit a6d4708e8169) on 2026-09-11; docker/compose was counted at ref main (commit 7c808c29c3bb) on 2026-09-07. See the counting methodology for ignored directories and analysis options.
Yes. This page shows the default branch for each repository. Use the interactive comparison tool to pick any public GitHub repository, branch, tag, or commit SHA for both sides and get a fresh side-by-side report.