This page compares the source lines of code (SLOC) of godotengine/godot and bevyengine/bevy 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-07, godotengine/godot contains 5,738,965 total lines (4,085,716 code) across 11,301 files, while bevyengine/bevy contains 553,959 total lines (461,329 code) across 2,156 files as of 2026-09-07. godotengine/godot is about 8.9x the size of bevyengine/bevy by code lines. Code size is not code quality: a larger count only means more source material, not a better or worse project.
| Metric | godotengine/godot | bevyengine/bevy |
|---|---|---|
| Files | 11,301 | 2,156 |
| Total lines | 5,738,965 | 553,959 |
| Code lines | 4,085,716 | 461,329 |
| Comment lines | 728,730 | 27,918 |
| Blank lines | 924,519 | 64,712 |
| Languages counted | 12 | 12 |
Top languages in godotengine/godot: C++ (34.5% of code), C Header (20.1% of code), PO File (15.3% of code). Top languages in bevyengine/bevy: Rust (97.6% of code), TOML (2.0% of code), SVG (0.2% of code). C++, C Header, PO File, C, C++ Header appear only in godotengine/godot's top languages; Rust, TOML, SVG, Shell, Pan appear only in bevyengine/bevy's top languages.
Methodology: both counts come from cached OctoCounts reports generated with tokei. godotengine/godot was counted at ref master (commit 34d06658a858) on 2026-09-07; bevyengine/bevy was counted at ref main (commit 7a21c21ecbce) 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.
godotengine/godot has more code: 4,085,716 code lines versus 461,329 for bevyengine/bevy, about 8.9x as much, based on cached OctoCounts reports as of 2026-09-07.
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 godotengine/godot, bevyengine/bevy, or any repository.
Methodology: both counts come from cached OctoCounts reports generated with tokei. godotengine/godot was counted at ref master (commit 34d06658a858) on 2026-09-07; bevyengine/bevy was counted at ref main (commit 7a21c21ecbce) 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.