This page compares the source lines of code (SLOC) of tokio-rs/tokio and async-rs/async-std 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, tokio-rs/tokio contains 85,026 total lines (60,608 code) across 539 files, while async-rs/async-std contains 18,552 total lines (14,817 code) across 267 files as of 2026-08-26. tokio-rs/tokio is about 4.1x the size of async-rs/async-std by code lines. Code size is not code quality: a larger count only means more source material, not a better or worse project.
| Metric | tokio-rs/tokio | async-rs/async-std |
|---|---|---|
| Files | 539 | 267 |
| Total lines | 85,026 | 18,552 |
| Code lines | 60,608 | 14,817 |
| Comment lines | 10,119 | 1,143 |
| Blank lines | 14,299 | 2,592 |
| Languages counted | 4 | 4 |
Top languages in tokio-rs/tokio: Rust (98.8% of code), TOML (1.1% of code), JSON (0.1% of code). Top languages in async-rs/async-std: Rust (99.2% of code), TOML (0.7% of code), Shell (0.1% of code). Rust, TOML, Markdown appear in both top language lists; JSON appears only in tokio-rs/tokio's top languages; Shell appears only in async-rs/async-std's top languages.
Methodology: both counts come from cached OctoCounts reports generated with tokei. tokio-rs/tokio was counted at ref master (commit ea91b33ca57f) on 2026-08-26; async-rs/async-std was counted at ref main (commit 844b55253152) 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.
tokio-rs/tokio has more code: 60,608 code lines versus 14,817 for async-rs/async-std, about 4.1x 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 tokio-rs/tokio, async-rs/async-std, or any repository.
Methodology: both counts come from cached OctoCounts reports generated with tokei. tokio-rs/tokio was counted at ref master (commit ea91b33ca57f) on 2026-08-26; async-rs/async-std was counted at ref main (commit 844b55253152) 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.