StackMap
Subscribe

open-code-review vs openqodex

Alibaba's battle-tested AI code-review CLI: deterministic pipelines + LLM agent, line-level comments, tuned rulesets (NPE, XSS, SQLi) — higher precision than general agents at ~1/9 the tokens. — versus — Local pre-push code review for coding agents: deterministic scanners (gitleaks, semgrep) plus separate Claude Code/Codex reviewer sessions, with a push gate. No account or key of its own.

The curated verdict

Both are AI code review CLIs combining deterministic checks with an LLM agent. Alibaba's targets PR review; OpenQodex gates the agent's own pushes locally.

open-code-reviewopenqodex
Stars49k1.1k
Forks3.6k76
LanguageGoTypeScript
LicenseApache-2.0Apache-2.0
Last activityyesterdayyesterday
Topicscodingcoding, evals
Curated connections43

open-code-review — the curator's take

Two years as Alibaba's internal review assistant before open-sourcing, and it shows: the hybrid architecture (deterministic checks + tool-using LLM agent) is tuned for precision over recall — fewer, better line-level comments instead of noise — and their 200-PR benchmark honestly reports the trade-off, including losing to general agents on recall. `ocr scan` reviews whole files, useful for auditing unfamiliar code with no diff. Bring your own endpoint (OpenAI/Anthropic-compatible). NOT a replacement for your coding agent's judgment on architecture — it's a defect-finder (NPE, thread-safety, XSS, SQLi rulesets), strongest on the bug classes it was fine-tuned for; the deliberate low-recall bias means a clean review is not a clean PR.

openqodex — the curator's take

Use it when agents write most of your code and you want a second, independent reviewer before every push, running on your existing Claude Code or Codex login. The writer agent never reviews its own change by default. Skip it on Windows (untested), or if you already run review in CI on PRs and don't want reviews to cost tokens locally. Cursor and Cline can trigger a review but can't be the reviewer.