chatbox vs Vane

chatbox and Vane share 10 technologies: React, SQLite, Tailwind CSS, tailwind-merge, sonner, Lucide, js-tiktoken, @mozilla/readability, officeparser, and Zod. 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.
chatbox383,291 lines written1,441 code files
Vane17,524 lines written158 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.
chatbox6.2% of its commits signed by AIWith Claude Code, Codex, Cursor, GitHub Copilot, and CodeRabbit
Vane0% of its commits signed by AI
ActivityFrom GitHub and its history, on the day SeeRepo read it.
chatboxLast push October 29, 20261,800 commits42,254 stars
VaneLast push September 1, 2026911 commits38,048 stars
TestsThe files that test the code, and the share of code files a test imports.
chatbox762 test files56.6% of its code files have a test that imports them
Vane0 test files

Frequently asked questions

Which is bigger, chatbox or Vane?
chatbox, with 383,291 lines written; Vane has 17,524.

The proof: chatboxai/chatbox's code at commit d17455c

Which has more GitHub stars, chatbox or Vane?
chatbox, with 42,254 stars; Vane has 38,048.

The proof: chatboxai/chatbox on GitHub

Which has more tests, chatbox or Vane?
chatbox, with 762 test files.

The proof: chatboxai/chatbox's code at commit d17455c

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

The proof: chatboxai/chatbox's commits on GitHub

Which has more commits signed by AI, chatbox or Vane?
chatbox: an AI signed 6.2% of its commits, with Claude Code, Codex, Cursor, GitHub Copilot, and CodeRabbit.

The proof: the commits each tool signed in chatboxai/chatbox

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 →