Rocket vs Axum: source lines of code compared

The Rocket vs Axum comparison on OctoCounts shows side-by-side source line counts for rwf2/Rocket and tokio-rs/axum, 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 rwf2/Rocket and tokio-rs/axum 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-10-31, rwf2/Rocket contains 47,393 total lines (35,529 code) across 431 files, while tokio-rs/axum contains 39,762 total lines (29,953 code) across 276 files as of 2026-11-15. rwf2/Rocket has about 1.2x the counted code lines of tokio-rs/axum 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.

Metricrwf2/Rockettokio-rs/axum
Files431276
Total lines47,39339,762
Code lines35,52929,953
Comment lines4,1863,838
Blank lines7,6785,971
Languages counted128

Top languages in rwf2/Rocket: Rust (92.5% of code), TOML (2.3% of code), CSS (1.9% of code). Top languages in tokio-rs/axum: Rust (95.3% of code), TOML (4.2% of code), Jinja2 (0.1% of code). Rust, TOML appear in both top language lists; CSS, Shell, Tera appear only in rwf2/Rocket's top languages; Jinja2, JavaScript, HTML appear only in tokio-rs/axum's top languages.

Methodology: both counts come from cached OctoCounts reports generated with tokei. rwf2/Rocket was counted at ref master (commit 3a54d079aef0) on 2026-10-31; tokio-rs/axum was counted at ref main (commit 2449f1600c66) on 2026-11-15. 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. rwf2/Rocket: 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. tokio-rs/axum: 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.

About this comparison

Background observations recorded on 2026-10-17; 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: rwf2/Rocket is the Rocket repository: a Rust web framework with its core, its procedural-macro codegen, documentation, and examples. tokio-rs/axum is the Axum repository: a Rust web framework maintained by the Tokio team, built to compose with the Tower service ecosystem, with its own modules, examples, and tests. Both are framework source trees within the Rust async ecosystem, counted on the dates above.

Both repositories are written in Rust, as the per-language tables confirm, so the counted difference is in structure rather than language: Rocket's tree centers on a batteries-included framework with its own codegen macros, while Axum's tree concentrates on routing and handlers composed from the shared Tower/Hyper layers.

A framework repository's size does not indicate request throughput, latency, or suitability for an application; those depend on the versioned crate and how it is used, not on the source tree's line count.

Sources: rwf2/Rocket repository · tokio-rs/axum repository. Statements verified 2026-10-17.

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.

Compare FAQ

Which has more lines of code, rwf2/Rocket or tokio-rs/axum?

As of 2026-10-31, rwf2/Rocket contains 47,393 total lines (35,529 code) across 431 files, while tokio-rs/axum contains 39,762 total lines (29,953 code) across 276 files as of 2026-11-15. rwf2/Rocket has about 1.2x the counted code lines of tokio-rs/axum 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.

Does more source lines of code mean more complexity?

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 rwf2/Rocket, tokio-rs/axum, or any repository.

How is this comparison calculated?

Methodology: both counts come from cached OctoCounts reports generated with tokei. rwf2/Rocket was counted at ref master (commit 3a54d079aef0) on 2026-10-31; tokio-rs/axum was counted at ref main (commit 2449f1600c66) on 2026-11-15. See the counting methodology for ignored directories and analysis options.

Can I compare a different branch, tag, or commit?

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.