The Axum vs Actix Web comparison on OctoCounts shows side-by-side source line counts for tokio-rs/axum and actix/actix-web, 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 tokio-rs/axum and actix/actix-web 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-15, tokio-rs/axum contains 39,762 total lines (29,953 code) across 276 files, while actix/actix-web contains 77,674 total lines (58,932 code) across 304 files as of 2026-11-15. actix/actix-web has about 2.0x 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.
| Metric | tokio-rs/axum | actix/actix-web |
|---|---|---|
| Files | 276 | 304 |
| Total lines | 39,762 | 77,674 |
| Code lines | 29,953 | 58,932 |
| Comment lines | 3,838 | 6,056 |
| Blank lines | 5,971 | 12,686 |
| Languages counted | 8 | 8 |
Top languages in tokio-rs/axum: Rust (95.3% of code), TOML (4.2% of code), Jinja2 (0.1% of code). Top languages in actix/actix-web: Rust (98.0% of code), TOML (1.5% of code), BASH (0.2% of code). Rust, TOML appear in both top language lists; Jinja2, JavaScript, HTML appear only in tokio-rs/axum's top languages; BASH, Just, Shell appear only in actix/actix-web's top languages.
Methodology: both counts come from cached OctoCounts reports generated with tokei. tokio-rs/axum was counted at ref main (commit 2449f1600c66) on 2026-11-15; actix/actix-web was counted at ref main (commit 97ea807a02b1) 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. 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. actix/actix-web: 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: tokio-rs/axum is the Axum repository: an ergonomic web framework built on the Tokio ecosystem's tower and hyper components. actix/actix-web is the Actix Web repository: a web framework with its own actor-model runtime layer underneath. Both are Rust web-framework source trees, measured under the rules and on the dates in the methodology line.
Both repositories are written in Rust, and the per-language tables reflect that on both sides; on this page the totals are the more informative number, since the language mix offers little contrast.
Axum's repository is comparatively thin over the shared Tokio ecosystem crates (which live in their own repositories), while Actix Web's repository carries its runtime layer in-tree — a structural difference visible only when the repositories are read, not from the counts alone.
Neither number measures request throughput or latency for a real service; both frameworks sit on top of asynchronous runtimes whose behavior depends on workload, configuration, and the ecosystem crates each application pulls in.
Sources: tokio-rs/axum repository · actix/actix-web 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-15, tokio-rs/axum contains 39,762 total lines (29,953 code) across 276 files, while actix/actix-web contains 77,674 total lines (58,932 code) across 304 files as of 2026-11-15. actix/actix-web has about 2.0x 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.
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 tokio-rs/axum, actix/actix-web, or any repository.
Methodology: both counts come from cached OctoCounts reports generated with tokei. tokio-rs/axum was counted at ref main (commit 2449f1600c66) on 2026-11-15; actix/actix-web was counted at ref main (commit 97ea807a02b1) on 2026-11-15. 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.