open-code-review vs hunk
Two of the top projects in Code review and testing, side by side: who leads on each score part and who each one suits, then setup, license, activity and what each review found.
open-code-review
CLI that reviews Git diffs with an LLM agent and line-level comments
hunk
Terminal diff viewer for reviewing code changes, with inline agent notes
Verdict
open-code-review ranks higher, 79 to 71. Of the 5 score parts we measure for both, open-code-review leads on 2, hunk on none and 3 are even.
- Adoptionopen-code-review leads by 35 points, 90 to 55: a wide gap.
- FreshnessEven at 100.
- Maintenanceopen-code-review leads by 4 points, 91 to 87: close to even.
- Easy to runEven at 50.
- Agent-readyEven at 70.
Pick open-code-review if you are
Teams adding LLM code review to local workflows or CI pipelines
- Deterministic file selection and bundling; each bundle runs as an isolated sub-agent
- Reviews workspace changes, branch ranges, single commits, or full files via `ocr scan`
Pick hunk if you are
Developers who review diffs or agent-written changes in the terminal
- Opens Git, Jujutsu and Sapling changes, plus GitHub PRs via bundled `hunk gh` with no gh CLI
- Works as a pager for git, jj and Sapling, and reads patches from stdin
| What we compare | open-code-review | hunk |
|---|---|---|
| Score parts, out of 100 | ||
| Adoption | 90, widely used | 55, popular |
| Freshness | 100, active | 100, active |
| Maintenance | 91, healthy | 87, healthy |
| Easy to run | 50, easy | 50, easy |
| Agent-ready | 70, partly | 70, partly |
| Facts from GitHub and the README | ||
| Stars | 47.8k | 9.6k |
| License | Apache-2.0 (permissive) | MIT (permissive) |
| Last commit | Oct 2026 | Oct 2026 |
| Last release | Oct 2026 | Oct 2026 |
| Language | Go | TypeScript |
| Docker | No | No |
| GPU | Not needed | Not needed |
| arm64 or Apple Silicon | Mentioned | Mentioned |
open-code-review
Open Code Review is a Go CLI (`ocr`) that reads a Git diff, groups related files into bundles, and runs each bundle through a tool-using LLM agent that produces structured review comments. File selection, rule matching, comment positioning and reflection are done by deterministic code rather than prompts. `ocr scan` reviews whole files when there is no diff, and delegation mode lets an existing coding agent do the review with its own model.
Who it is for: Teams adding LLM code review to local workflows or CI pipelines
Strengths
- Deterministic file selection and bundling; each bundle runs as an isolated sub-agent
- Reviews workspace changes, branch ranges, single commits, or full files via `ocr scan`
- Sessions can be resumed and browsed in a viewer; JSON output for automation
- Plugins for Claude Code, Codex, Cursor, Kimi Code, OpenCode; CI docs for GitHub, GitLab, Gerrit
Weaknesses
- Requires Git >= 2.41 and a configured LLM endpoint, unless delegation mode is used
- Recall is lower than general-purpose agents by the README's own benchmark
- Benchmark figures are published by the project itself, not independently verified
- No Docker or Compose files detected
- no GPU
- Needs Git >= 2.41, LLM provider API
- Models: configurable LLM providers, custom providers
hunk
Hunk is an interactive terminal diff viewer built on OpenTUI and Pierre diffs. It opens Git, Jujutsu and Sapling changes, GitHub pull requests, raw patches from stdin, or two files, in a multi-file stream with a sidebar. A coding agent can use the hunk-review skill to attach notes to a live session, and they show beside the code.
Who it is for: Developers who review diffs or agent-written changes in the terminal
Strengths
- Opens Git, Jujutsu and Sapling changes, plus GitHub PRs via bundled `hunk gh` with no gh CLI
- Works as a pager for git, jj and Sapling, and reads patches from stdin
- Standalone binary via install script, Homebrew, mise or Nix; no Node.js needed
- Extension API and embeddable OpenTUI diff component (`hunkdiff/opentui`)
Weaknesses
- No structural diffing; the README's own comparison table marks it as missing
- No prebuilt binaries for Windows arm64 or musl Linux such as Alpine
- GitHub Enterprise is not supported
- Extension API is experimental and may break between minor releases
- no GPU
- Needs Git (recommended), Node.js 22+ (npm install only), GH_TOKEN or GITHUB_TOKEN (private repos)
More in Code review and testing
Building with these?
We help teams pick an open-source AI stack and run it in production. Client work never changes a rank.