head to head · open source
code-review-graph vs tuicr
code-review-graph has 32,563 GitHub stars, 2,964 forks, 163 open issues and last shipped 5 days ago. tuicr has 3,502 stars, 326 forks, 133 open issues and last shipped 3 days ago. code-review-graph leads on adoption by 830% (32,563 vs 3,502 stars). code-review-graph is written in Python under MIT; tuicr is written in Rust under MIT. code-review-graph has attracted 9% as many forks as stars, tuicr 9%. tuicr was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 1 topic tag (code-review), so they are genuine substitutes rather than adjacent tools.
Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.
← all 20902 open source comparisons
Side by side
| code-review-graph | tuicr | |
|---|---|---|
| GitHub stars | ★ 33K | ★ 3.5K |
| License | MIT | MIT |
| Written in | Python | Rust |
| Last push | 2026-10-29 | 2026-10-31 |
| Forks | ⑂ 3.0K | ⑂ 326 |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick code-review-graph if
- You weight community size — 33K stars and counting
- You want the MIT license terms
- Your stack matches Python
- You value the larger contributor base for long-term maintenance
pick tuicr if
- You want the tuicr feature set and don't need the biggest community
- You prefer the MIT license terms
- Your stack matches Rust
- You evaluated both and tuicr fits your workflow better
About code-review-graph
code review graph Stop burning tokens. Start reviewing smarter. English 简体中文 日本語 한국어 हिन्दी Usage · Commands · FAQ · Troubleshooting · GitHub Action · Reproducing the benchmarks · Roadmap AI coding tools can end up re reading large parts of your codebase on review tasks. code review graph fixes that. It builds a structural map of your code with Tree sitter, tracks changes incrementally, and gives your AI assistant precise context via MCP so it reads only what matters. Quick Start One command sets up everything. install detects which AI coding tools you have, writes the correct MCP configuration for each one…
read the full code-review-graph overview →
About tuicr
tuicr A code review TUI with vim keybindings. Export to GitHub, GitLab, Gitea, Bitbucket, Azure DevOps, Gerrit, or clipboard. [!TIP] Pronounced "tweaker". What it does GitHub style continuous diff in the terminal. Scroll through every changed file in one stream. PR style comments at the line, range, file, and review level. Review tracking at file or hunk granularity, persisted across sessions. Three export targets: push a real review to GitHub, GitLab, Gitea, Bitbucket, Azure DevOps, or Gerrit, copy structured markdown to your clipboard, or pipe to stdout. Works with git, jj, and mercurial. Reviews uncommitted…
read the full tuicr overview →
More in Developer Tools
Related comparisons
More Version Control & Collaboration projects
Compare either of these against the rest of the Version Control & Collaboration field.
Frequently asked questions
Is code-review-graph or tuicr more popular?
code-review-graph has 32,563 GitHub stars and tuicr has 3,502. code-review-graph has the larger community by that measure.
Are code-review-graph and tuicr free?
Both are open source. code-review-graph is licensed under MIT and tuicr under MIT. Neither carries a licence fee.
What is the difference between code-review-graph and tuicr?
code-review-graph is written in Python and tuicr in Rust. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.
Which should I choose, code-review-graph or tuicr?
Choose code-review-graph if you want the larger community (32,563 stars) or its MIT licence terms. Choose tuicr if its feature set, stack or MIT licence fits better. Both are self-hostable.