Bun vs Deno: source lines of code compared

This page compares the source lines of code (SLOC) of oven-sh/bun and denoland/deno 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-06, oven-sh/bun contains 1,959,331 total lines (1,465,280 code) across 4,082 files, while denoland/deno contains 1,191,325 total lines (945,391 code) across 2,021 files as of 2026-09-07. oven-sh/bun is about 1.5x 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.

Metricoven-sh/bundenoland/deno
Files4,0822,021
Total lines1,959,3311,191,325
Code lines1,465,280945,391
Comment lines332,472170,829
Blank lines161,57975,105
Languages counted1212

Top languages in oven-sh/bun: Rust (54.0% of code), C (13.7% of code), C++ (11.1% of code). Top languages in denoland/deno: Rust (53.2% of code), JavaScript (29.4% of code), TypeScript (15.0% of code). Rust, C, TypeScript, JavaScript appear in both top language lists; C++ appears only in oven-sh/bun's top languages; TOML appears only in denoland/deno's top languages.

Methodology: both counts come from cached OctoCounts reports generated with tokei. oven-sh/bun was counted at ref d316760e8cae0d69ae927898d5afc933ecf34671 (commit d316760e8cae) on 2026-09-06; denoland/deno was counted at ref main (commit 83bb8d578050) 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.

Compare FAQ

Which has more lines of code, oven-sh/bun or denoland/deno?

oven-sh/bun has more code: 1,465,280 code lines versus 945,391 for denoland/deno, about 1.5x as much, based on cached OctoCounts reports as of 2026-09-07.

Does more source lines of code mean more complexity?

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, denoland/deno, or any repository.

How is this comparison calculated?

Methodology: both counts come from cached OctoCounts reports generated with tokei. oven-sh/bun was counted at ref d316760e8cae0d69ae927898d5afc933ecf34671 (commit d316760e8cae) on 2026-09-06; denoland/deno was counted at ref main (commit 83bb8d578050) on 2026-09-07. See the counting methodology for ignored directories and analysis options.

Can I compare a different branch, tag, or commit?

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.