Bun vs Deno: source lines of code compared

The Bun vs Deno comparison on OctoCounts shows side-by-side source line counts for oven-sh/bun and denoland/deno, 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 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-11-16, oven-sh/bun contains 3,219,843 total lines (2,638,181 code) across 7,240 files, while denoland/deno contains 1,194,932 total lines (948,404 code) across 2,020 files as of 2026-11-02. oven-sh/bun has about 2.8x the counted code lines of denoland/deno 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.

Metricoven-sh/bundenoland/deno
Files7,2402,020
Total lines3,219,8431,194,932
Code lines2,638,181948,404
Comment lines344,607171,109
Blank lines237,05575,419
Languages counted3315

Top languages in oven-sh/bun: Rust (70.0% of code), TypeScript (8.1% of code), C++ (7.6% of code). Top languages in denoland/deno: Rust (53.3% of code), JavaScript (29.4% of code), TypeScript (14.9% of code). Rust, TypeScript, C, 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 main (commit 5f3f8fe483e7) on 2026-11-16; denoland/deno was counted at ref main (commit e7b39ebd55c8) on 2026-11-02. 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. denoland/deno: 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.

About this comparison

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 runtime, bundler, test runner, and package manager, written in Zig around a vendored JavaScriptCore/WebKit tree. denoland/deno is the Deno repository: the runtime, built in Rust on top of V8, with its standard library and toolchain. Both are all-in-one runtime monorepos, counted on the dates shown in the methodology line above.

The per-language tables show the implementation-language contrast directly — Zig-dominated on one side, Rust-dominated on the other — which is the counting-engine equivalent of each project's well-known choice of systems language.

Both trees include third-party dependency code alongside the project's own — Bun notably vendors the WebKit/JSC engine it runs on — so these totals are not 'lines written by the project', and they say nothing about runtime speed or memory use.

Sources: oven-sh/bun repository (Zig runtime and vendored WebKit) · denoland/deno repository (Rust runtime on V8). 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.

Compare FAQ

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

As of 2026-11-16, oven-sh/bun contains 3,219,843 total lines (2,638,181 code) across 7,240 files, while denoland/deno contains 1,194,932 total lines (948,404 code) across 2,020 files as of 2026-11-02. oven-sh/bun has about 2.8x the counted code lines of denoland/deno 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.

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 main (commit 5f3f8fe483e7) on 2026-11-16; denoland/deno was counted at ref main (commit e7b39ebd55c8) on 2026-11-02. 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.