neohtop vs jan

neohtop and jan share 5 technologies: @tauri-apps/api, Tauri, Tailwind CSS, Lucide, and png. neohtop is written in Svelte and jan 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.
neohtop17,519 lines written213 code files
jan515,841 lines written992 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.
neohtop0.4% of its commits signed by AIWith Cursor
jan0.5% of its commits signed by AIWith GitHub Copilot, Claude Code, Cursor, Factory, Jules, and Aider
ActivityFrom GitHub and its history, on the day SeeRepo read it.
neohtopLast push October 30, 2026263 commits9,515 stars
janLast push November 13, 20267,582 commits45,706 stars
TestsThe files that test the code, and the share of code files a test imports.
neohtop2 test files0.5% of its code files have a test that imports them
jan583 test files51.4% of its code files have a test that imports them

Frequently asked questions

Which is bigger, neohtop or jan?
jan, with 515,841 lines written; neohtop has 17,519.

The proof: janhq/jan's code at commit ea98bd3

Which has more GitHub stars, neohtop or jan?
jan, with 45,706 stars; neohtop has 9,515.

The proof: janhq/jan on GitHub

Which has more tests, neohtop or jan?
jan, with 583 test files; neohtop has 2.

The proof: janhq/jan's code at commit ea98bd3

Which was updated more recently, neohtop or jan?
jan: its last push was on November 13, 2026, and neohtop's on October 30, 2026.

The proof: janhq/jan's commits on GitHub

Which has more commits signed by AI, neohtop or jan?
jan: an AI signed 0.5% of its commits, with GitHub Copilot, Claude Code, Cursor, Factory, Jules, and Aider; in neohtop, 0.4%.

The proof: the commits each tool signed in janhq/jan

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 →