open-code-review vs react-doctor
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
react-doctor
CLI that scans React codebases for state, performance, security and accessibility issues
Verdict
open-code-review ranks higher, 79 to 72. Of the 5 score parts we measure for both, open-code-review leads on 2, react-doctor on 1 and 2 are even.
- Adoptionopen-code-review leads by 15 points, 90 to 75: a wide gap.
- FreshnessEven at 100.
- Maintenancereact-doctor leads by 4 points, 95 to 91: close to even.
- Easy to runopen-code-review leads by 17 points, 50 to 33: a wide gap.
- 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 react-doctor if you are
React and React Native developers wanting code checks locally and in CI
- Runs with one npx command from the project root, no setup needed
- Deterministic rules rather than LLM-generated findings
| What we compare | open-code-review | react-doctor |
|---|---|---|
| Score parts, out of 100 | ||
| Adoption | 90, widely used | 75, popular |
| Freshness | 100, active | 100, active |
| Maintenance | 91, healthy | 95, healthy |
| Easy to run | 50, easy | 33, some setup |
| Agent-ready | 70, partly | 70, partly |
| Facts from GitHub and the README | ||
| Stars | 47.8k | 15k |
| License | Apache-2.0 (permissive) | custom license (read the license) |
| 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 | Not stated |
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
react-doctor
React Doctor runs deterministic checks over a React project and reports issues in state and effects, performance, architecture, security, accessibility and maintainability. It covers Next.js, Vite, Astro, TanStack, React Native and Expo. It also installs as a skill for coding agents, runs on pull requests in CI, and can record a Chrome DevTools performance trace of a running app.
Who it is for: React and React Native developers wanting code checks locally and in CI
Strengths
- Runs with one npx command from the project root, no setup needed
- Deterministic rules rather than LLM-generated findings
- Agent skill installer supports Claude Code, Cursor, Codex and OpenCode
- Rules configurable in doctor.config.ts; CI installer reports issues each PR introduces
Weaknesses
- React-only; no support for other frameworks beyond the listed React stacks
- CLI collects crash reports and anonymous usage data unless opted out
- Runtime trace scan needs a running app and a Chrome DevTools trace
- README does not list the number of rules or their names
- no GPU
- Needs Node.js, npm
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.