This page compares the source lines of code (SLOC) of oven-sh/bun 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-14, oven-sh/bun contains 3,812,278 total lines (2,934,912 code) across 17,806 files, while nodejs/node contains 12,545,334 total lines (9,931,243 code) across 18,425 files as of 2026-09-14. nodejs/node is about 3.4x the size of oven-sh/bun by code lines. Code size is not code quality: a larger count only means more source material, not a better or worse project.
| Metric | oven-sh/bun | nodejs/node |
|---|---|---|
| Files | 17,806 | 18,425 |
| Total lines | 3,812,278 | 12,545,334 |
| Code lines | 2,934,912 | 9,931,243 |
| Comment lines | 546,337 | 1,400,756 |
| Blank lines | 331,029 | 1,213,335 |
| Languages counted | 12 | 12 |
Top languages in oven-sh/bun: Rust (27.1% of code), TypeScript (26.5% of code), JavaScript (20.7% 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, TypeScript, JavaScript, JSON appear only in oven-sh/bun'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. oven-sh/bun was counted at ref main (commit d27fef0b9082) on 2026-09-14; nodejs/node was counted at ref main (commit e5778f78c51e) on 2026-09-14. 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,931,243 code lines versus 2,934,912 for oven-sh/bun, about 3.4x as much, based on cached OctoCounts reports as of 2026-09-14.
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 oven-sh/bun, nodejs/node, or any repository.
Methodology: both counts come from cached OctoCounts reports generated with tokei. oven-sh/bun was counted at ref main (commit d27fef0b9082) on 2026-09-14; nodejs/node was counted at ref main (commit e5778f78c51e) on 2026-09-14. 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.