This page compares the source lines of code (SLOC) of argoproj/argo-cd and fluxcd/flux2 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-08, argoproj/argo-cd contains 929,688 total lines (843,536 code) across 4,372 files, while fluxcd/flux2 contains 51,067 total lines (35,469 code) across 548 files as of 2026-08-26. argoproj/argo-cd is about 24x the size of fluxcd/flux2 by code lines. Code size is not code quality: a larger count only means more source material, not a better or worse project.
| Metric | argoproj/argo-cd | fluxcd/flux2 |
|---|---|---|
| Files | 4,372 | 548 |
| Total lines | 929,688 | 51,067 |
| Code lines | 843,536 | 35,469 |
| Comment lines | 36,905 | 9,089 |
| Blank lines | 49,247 | 6,509 |
| Languages counted | 12 | 9 |
Top languages in argoproj/argo-cd: Go (49.0% of code), YAML (40.8% of code), TSX (3.7% of code). Top languages in fluxcd/flux2: Go (83.8% of code), YAML (14.9% of code), Shell (0.6% of code). Go, YAML, JSON appear in both top language lists; TSX, Lua appear only in argoproj/argo-cd's top languages; Shell, Makefile appear only in fluxcd/flux2's top languages.
Methodology: both counts come from cached OctoCounts reports generated with tokei. argoproj/argo-cd was counted at ref b079641e62e979aae012503ba98bbc683423492a (commit b079641e62e9) on 2026-09-08; fluxcd/flux2 was counted at ref main (commit da2d22d36901) on 2026-08-26. 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.
argoproj/argo-cd has more code: 843,536 code lines versus 35,469 for fluxcd/flux2, about 24x as much, based on cached OctoCounts reports as of 2026-09-08.
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 argoproj/argo-cd, fluxcd/flux2, or any repository.
Methodology: both counts come from cached OctoCounts reports generated with tokei. argoproj/argo-cd was counted at ref b079641e62e979aae012503ba98bbc683423492a (commit b079641e62e9) on 2026-09-08; fluxcd/flux2 was counted at ref main (commit da2d22d36901) on 2026-08-26. 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.