This page compares the source lines of code (SLOC) of denoland/deno and nodejs/node 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, denoland/deno contains 1,191,325 total lines (945,391 code) across 2,021 files, while nodejs/node contains 12,543,725 total lines (9,926,652 code) across 18,407 files as of 2026-09-07. nodejs/node is about 11x the size of denoland/deno by code lines. Code size is not code quality: a larger count only means more source material, not a better or worse project.
| Metric | denoland/deno | nodejs/node |
|---|---|---|
| Files | 2,021 | 18,407 |
| Total lines | 1,191,325 | 12,543,725 |
| Code lines | 945,391 | 9,926,652 |
| Comment lines | 170,829 | 1,403,253 |
| Blank lines | 75,105 | 1,213,820 |
| Languages counted | 12 | 12 |
Top languages in denoland/deno: Rust (53.2% of code), JavaScript (29.4% of code), TypeScript (15.0% of code). Top languages in nodejs/node: C Header (20.9% of code), GNU Style Assembly (19.1% of code), Perl (17.5% of code). C appears in both top language lists; Rust, JavaScript, TypeScript, TOML appear only in denoland/deno's top languages; C Header, GNU Style Assembly, Perl, C++ appear only in nodejs/node's top languages.
Methodology: both counts come from cached OctoCounts reports generated with tokei. denoland/deno was counted at ref main (commit 83bb8d578050) on 2026-09-07; nodejs/node was counted at ref main (commit 6f38736d63cb) 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.
nodejs/node has more code: 9,926,652 code lines versus 945,391 for denoland/deno, about 11x 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 denoland/deno, nodejs/node, or any repository.
Methodology: both counts come from cached OctoCounts reports generated with tokei. denoland/deno was counted at ref main (commit 83bb8d578050) on 2026-09-07; nodejs/node was counted at ref main (commit 6f38736d63cb) 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.