This page compares the source lines of code (SLOC) of apache/maven and gradle/gradle 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-08-26, apache/maven contains 253,607 total lines (148,169 code) across 1,898 files, while gradle/gradle contains 1,793,851 total lines (1,184,650 code) across 15,339 files as of 2026-08-26. gradle/gradle is about 8.0x the size of apache/maven by code lines. Code size is not code quality: a larger count only means more source material, not a better or worse project.
| Metric | apache/maven | gradle/gradle |
|---|---|---|
| Files | 1,898 | 15,339 |
| Total lines | 253,607 | 1,793,851 |
| Code lines | 148,169 | 1,184,650 |
| Comment lines | 74,989 | 383,925 |
| Blank lines | 30,449 | 225,276 |
| Languages counted | 9 | 12 |
Top languages in apache/maven: Java (89.3% of code), XML (6.9% of code), Apache Velocity (3.2% of code). Top languages in gradle/gradle: Groovy (45.6% of code), Java (43.6% of code), Kotlin (8.9% of code). Java, XML appear in both top language lists; Apache Velocity, Batch, Shell appear only in apache/maven's top languages; Groovy, Kotlin, C Header appear only in gradle/gradle's top languages.
Methodology: both counts come from cached OctoCounts reports generated with tokei. apache/maven was counted at ref master (commit cee6a96ccfbf) on 2026-08-26; gradle/gradle was counted at ref master (commit 1728de6b7ef8) 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.
gradle/gradle has more code: 1,184,650 code lines versus 148,169 for apache/maven, about 8.0x as much, based on cached OctoCounts reports as of 2026-08-26.
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 apache/maven, gradle/gradle, or any repository.
Methodology: both counts come from cached OctoCounts reports generated with tokei. apache/maven was counted at ref master (commit cee6a96ccfbf) on 2026-08-26; gradle/gradle was counted at ref master (commit 1728de6b7ef8) 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.