The Bun vs Node.js comparison on OctoCounts shows side-by-side source line counts for oven-sh/bun and nodejs/node, 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 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-11-16, oven-sh/bun contains 3,219,843 total lines (2,638,181 code) across 7,240 files, while nodejs/node contains 13,346,520 total lines (10,506,289 code) across 21,538 files as of 2026-11-16. nodejs/node has about 4.0x the counted code lines of oven-sh/bun 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 | oven-sh/bun | nodejs/node |
|---|---|---|
| Files | 7,240 | 21,538 |
| Total lines | 3,219,843 | 13,346,520 |
| Code lines | 2,638,181 | 10,506,289 |
| Comment lines | 344,607 | 1,485,822 |
| Blank lines | 237,055 | 1,354,409 |
| Languages counted | 33 | 54 |
Top languages in oven-sh/bun: Rust (70.0% of code), TypeScript (8.1% of code), C++ (7.6% of code). Top languages in nodejs/node: C Header (23.6% of code), GNU Style Assembly (18.7% of code), Perl (17.6% of code). C++, C appear in both top language lists; Rust, TypeScript, JavaScript appear only in oven-sh/bun's top languages; C Header, GNU Style Assembly, Perl 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 5f3f8fe483e7) on 2026-11-16; nodejs/node was counted at ref main (commit d3c404896285) on 2026-11-16. 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. oven-sh/bun: 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. nodejs/node: 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: oven-sh/bun is the Bun repository: the JavaScript/TypeScript runtime and toolkit, written predominantly in Zig with C++ components, on top of the JavaScriptCore engine it builds against. nodejs/node is the Node.js repository: the runtime built on V8, with its C++ core, JavaScript standard library, and test suites. Both are JavaScript runtime source trees, but the per-language tables show different implementation languages, and both repositories were taken on the dates above.
The language split is the headline of this comparison: Bun's counted code is predominantly Zig, while Node.js's is predominantly C++ with a large JavaScript layer — each project's chosen implementation language for the same job of hosting JavaScript.
Repository size says nothing about runtime speed, memory use, or compatibility with existing packages — those are properties of the shipped runtimes, and both projects change quickly. Treat the counts as a measure of each source tree's reading and maintenance surface.
Sources: oven-sh/bun repository · nodejs/node 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-16, oven-sh/bun contains 3,219,843 total lines (2,638,181 code) across 7,240 files, while nodejs/node contains 13,346,520 total lines (10,506,289 code) across 21,538 files as of 2026-11-16. nodejs/node has about 4.0x the counted code lines of oven-sh/bun 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 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 5f3f8fe483e7) on 2026-11-16; nodejs/node was counted at ref main (commit d3c404896285) on 2026-11-16. 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.