The Argo CD vs Flux comparison on OctoCounts shows side-by-side source line counts for argoproj/argo-cd and fluxcd/flux2, counted under the rules and on the dates stated below: files, total lines, code lines, comment lines, blank lines, and per-language totals, pinned to the exact commits listed below.
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-11-16, argoproj/argo-cd contains 1,001,512 total lines (906,844 code) across 4,601 files, while fluxcd/flux2 contains 58,617 total lines (41,009 code) across 594 files as of 2026-11-16. argoproj/argo-cd has about 22x the counted code lines of fluxcd/flux2 under the same engine and counting rules. 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,601 | 594 |
| Total lines | 1,001,512 | 58,617 |
| Code lines | 906,844 | 41,009 |
| Comment lines | 40,983 | 10,438 |
| Blank lines | 53,685 | 7,170 |
| Languages counted | 21 | 9 |
Top languages in argoproj/argo-cd: Go (48.8% of code), YAML (40.7% of code), TSX (4.1% of code). Top languages in fluxcd/flux2: Go (82.9% of code), YAML (15.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 master (commit e0dc5a734886) on 2026-11-16; fluxcd/flux2 was counted at ref main (commit d7e87c943d61) on 2026-11-16. See the counting methodology for ignored directories and analysis options.
Both reports use the same engine and effective counting rules. Repository declarations, when enabled, are specific to each repository. argoproj/argo-cd: tokei-15.0.0, policy directories-v1; docs excluded, tests excluded, generated excluded. Excluded directory names: .cache, .generated, .git, .next, __tests__, build, dist, doc, docs, documentation, fixtures, gen, generated, node_modules, target, test, tests, vendor. Ignored languages: none. Repository declarations: off. Exclusions are rule-based; they do not prove that every test, document or generated file was removed. fluxcd/flux2: tokei-15.0.0, policy directories-v1; docs excluded, tests excluded, generated excluded. Excluded directory names: .cache, .generated, .git, .next, __tests__, build, dist, doc, docs, documentation, fixtures, gen, generated, node_modules, target, test, tests, vendor. Ignored languages: none. Repository declarations: off. Exclusions are rule-based; they do not prove that every test, document or generated file was removed.
Background observations recorded on 2026-09-16; language descriptions here are historical context, not claims about the current filtered shares. Use this page's measured language breakdown for current counts. Repository layout before counting filters: argoproj/argo-cd is the Argo CD repository — the declarative GitOps continuous-delivery tool for Kubernetes, written in Go with a web UI layer in TypeScript. fluxcd/flux2 is the Flux repository — the GitOps toolkit's CLI and controllers, written in Go. Both repositories are Kubernetes GitOps tool source trees, counted on the dates in the methodology line above.
The per-language tables show Go dominating both trees, as expected for Kubernetes ecosystem tools whose controllers run against the Kubernetes API; Argo CD's table additionally carries a visible TypeScript share from its bundled web interface.
Both repositories package their CLI and their cluster-side components in one tree, so each total measures a complete operator-style tool — client and controllers together — rather than a single binary.
Line counts do not measure GitOps correctness or which tool fits a delivery pipeline: that depends on each tool's declared configuration model, how a team structures environments, and operational practices — not on repository size.
Sources: argoproj/argo-cd repository · fluxcd/flux2 repository. Statements verified 2026-09-16.
Evidence and next steps:
Saved reports remain subject to cache cleanup and replacement. Export their JSON for durable citation; live report URLs can change.
Note: code size is not code quality. OctoCounts only reports reproducible line counts and makes no claim that either project is better.
As of 2026-11-16, argoproj/argo-cd contains 1,001,512 total lines (906,844 code) across 4,601 files, while fluxcd/flux2 contains 58,617 total lines (41,009 code) across 594 files as of 2026-11-16. argoproj/argo-cd has about 22x the counted code lines of fluxcd/flux2 under the same engine and counting rules. Code size is not code quality: a larger count only means more source material, not a better or worse project.
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 master (commit e0dc5a734886) on 2026-11-16; fluxcd/flux2 was counted at ref main (commit d7e87c943d61) on 2026-11-16. 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.