n8n vs dexter

n8n and dexter share 5 technologies: SQLite, lru-cache, Zod, LangChain, and turndown. Both are written in TypeScript.

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.
n8n5,241,398 lines written14,224 code files
dexter27,217 lines written184 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.
n8n14.4% of its commits signed by AIWith Claude Code, Cursor, GitHub Copilot, Codex, and CodeRabbit
dexter9.6% of its commits signed by AIWith Cursor and Claude Code
ActivityFrom GitHub and its history, on the day SeeRepo read it.
n8nLast push November 4, 202626,047 commits209,517 stars
dexterLast push September 23, 2026471 commits27,784 stars
TestsThe files that test the code, and the share of code files a test imports.
n8n10,704 test files53.7% of its code files have a test that imports them
dexter19 test files13% of its code files have a test that imports them

Frequently asked questions

Which is bigger, n8n or dexter?
n8n, with 5,241,398 lines written; dexter has 27,217.

The proof: n8n-io/n8n's code at commit d5e7db2

Which has more GitHub stars, n8n or dexter?
n8n, with 209,517 stars; dexter has 27,784.

The proof: n8n-io/n8n on GitHub

Which has more tests, n8n or dexter?
n8n, with 10,704 test files; dexter has 19.

The proof: n8n-io/n8n's code at commit d5e7db2

Which was updated more recently, n8n or dexter?
n8n: its last push was on November 4, 2026, and dexter's on September 23, 2026.

The proof: n8n-io/n8n's commits on GitHub

Which has more commits signed by AI, n8n or dexter?
n8n: an AI signed 14.4% of its commits, with Claude Code, Cursor, GitHub Copilot, Codex, and CodeRabbit; in dexter, 9.6%.

The proof: the commits each tool signed in n8n-io/n8n

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 →