deno vs helix

deno and helix share 3 technologies: Tokio, crossterm, and log. Both are written in Rust.

Read it as markdown

What they share and what sets them apart

Side by side

SizeLines written by people and agents, without generated ones; code files, without tests.
deno1,217,015 lines written1,355 code files
helix108,689 lines written215 code files
Who writes itA commit counts as AI's when it carries its signature: a Co-Authored-By line, its author name or the merge of its branch.
deno2.4% of its commits signed by AIWith Claude Code, GitHub Copilot, Cursor, and Codex
helix0% of its commits signed by AIWith Claude Code
ActivityFrom GitHub and its history, on the day SeeRepo read it.
denoLast push October 29, 202617,392 commits108,801 stars
helixLast push September 29, 20267,621 commits46,818 stars
TestsThe files that test the code, and the share of code files a test imports.
deno4,394 test files6.1% of its code files have a test that imports them
helix80 test files2.3% of its code files have a test that imports them

Frequently asked questions

Which is bigger, deno or helix?
deno, with 1,217,015 lines written; helix has 108,689.

The proof: denoland/deno's code at commit e7b39eb

Which has more GitHub stars, deno or helix?
deno, with 108,801 stars; helix has 46,818.

The proof: denoland/deno on GitHub

Which has more tests, deno or helix?
deno, with 4,394 test files; helix has 80.

The proof: denoland/deno's code at commit e7b39eb

Which was updated more recently, deno or helix?
deno: its last push was on October 29, 2026, and helix's on September 29, 2026.

The proof: denoland/deno's commits on GitHub

Which has more commits signed by AI, deno or helix?
deno: an AI signed 2.4% of its commits, with Claude Code, GitHub Copilot, Cursor, and Codex.

The proof: the commits each tool signed in denoland/deno

See inside your code, today.

Paste your repo and see it drawn, part by part: a medium one in under a minute.

Free, no account.

Or look inside SeeRepo's own →