All Articles

Unblocked ranked the highest performing code review tool

Martian’s open Code Review Bench evaluates AI review tools on the same 50 real pull requests containing 158 known bugs. Unblocked caught more bugs overall, including more critical and high-severity bugs, than any other tool in Martian’s published results.

Unblocked ranked the highest performing code review tool
108 of 158Known bugs caughtMore than any tool in Martian's published results
66.2Overall scoreHigher than any tool in Martian's published results; next best 65.1
10 of 12Critical bugs caughtTied for the most among the tools compared
Critical and high-severity bugs caught, of 66
Every engineer knows some bugs matter more than others. A broken authentication check is far worse than a typo on the marketing website.
Unblocked55 of 66 · 83%
Qodo Deep49
Augment49
Cubic48
GitHub Copilot47
CodeRabbit42
Cursor Bugbot40
Greptile38
Claude Code35
Devin33
Unblocked caught six more critical and high-severity bugs than the next best tools we compared, Qodo Deep and Augment.

How to read these numbers. Martian built Code Review Bench and publishes the results of the other tools on its leaderboard. This post compares Unblocked with a selection of them, including the top three. We ran Unblocked through the same published pipeline and judge, on public copies of the same 50 pull requests, and every Unblocked review is public. Unblocked is not yet listed on Martian's own leaderboard. See how it was measured.

All 158 bugs#

Across all 158 known bugs, Unblocked caught 108, or 68.4%. GitHub Copilot came next at 66.5%, with Cubic, Augment and Qodo Deep close behind at about 65%.

Share of the 158 known bugs each tool caught
Unblocked68.4% · 108 of 158
GitHub Copilot66.5%
Cubic65.8%
Augment65.2%
Qodo Deep64.6%
CodeRabbit59.5%
Greptile51.3%
Claude Code48.1%
Cursor Bugbot46.8%
Devin41.1%
The overall score weighs bugs caught against issues that match no known bug. Unblocked's is the highest, 66.2 against Qodo Deep's 65.1.

What this means for your team#

A benchmark is only useful if it says something about your own pull requests. Here is what these results mean in practice.

10 of 12Critical bugs caughtAmong them, a blocked-email check that could be sidestepped by changing letter case, and a background job that fetched whatever URL a site setting held without checking it.
3.7Not a flood of commentsUnblocked raised about 3.7 issues per pull request, close to Cubic (3.4) and Augment (3.5), and well below GitHub Copilot (5.5) and CodeRabbit (5.8).
64%+Consistent across all five projectsUnblocked caught at least 64% of the bugs in each project, from TypeScript to Java. Every other tool fell below 60% in at least one.

Try Unblocked on your next pull request →

Head to head on the most serious bugs#

Pick any tool to compare the two on critical and high-severity bugs.

Critical and high-severity bugs caught
on serious bugs
Critical · 12
Unblocked83% · 10
Claude Code58% · 7
High · 54
Unblocked83% · 45
Claude Code52% · 28
Unblocked caught 20 more critical and high-severity bugs than Claude Code.

Test dataset#

Five open-source projects in five languages, ten pull requests from each. Each row shows how many of that project's known bugs Unblocked caught, and links to the public copy of the project where every Unblocked review can be read.

Python
Error tracking and performance monitoring
67%
22 of 33 bugs caught
TypeScript
Open-source scheduling infrastructure
76%
28 of 37 bugs caught
Go
Monitoring and observability platform
64%
16 of 25 bugs caught
Java
Identity and access management
64%
16 of 25 bugs caught
Ruby
Community discussion platform
68%
26 of 38 bugs caught

How Unblocked catches them#

Unblocked Code Review has two modes.

  • Standard mode - the Unblocked default that tends to post fewer comments.
  • Deep mode - which is the basis for this benchmark and built specifically to miss as few bugs as possible. This is typically used with teams where agents write much of the code and a missed bug costs more than an extra comment.

Deep mode reasons about what the pull request is trying to do, reviews it from several perspectives and checks each finding against the code before posting it.

The scoreboard and how it was measured#

The overall score is the ranking Martian's leaderboard uses by default. It combines bugs caught and comment accuracy, counting bugs caught twice as heavily (an F2 score). Comment accuracy is the share of a tool's raised issues that matched one of the 158 known bugs.

ToolOverall scoreBugs caught
Unblocked66.268.4%
Qodo Deep65.164.6%
Cubic64.965.8%
Augment64.065.2%
GitHub Copilot58.066.5%
Greptile51.251.3%
CodeRabbit51.159.5%
Cursor Bugbot48.646.8%
Claude Code47.748.1%
Devin44.841.1%

Code Review Bench is open source and maintained by Martian. Its 50 pull requests come from Cal.com, Sentry, Grafana, Keycloak and Discourse, ten from each. Each one reintroduces a real change that shipped bugs the project later fixed.

A bug counts as caught when a review comment identifies it. Every tool is scored against the same answer key by the same AI judge. One comment can raise more than one issue, and each issue is graded on its own.

The other tools' results are the ones Martian has published, using each tool's best-scoring version; this post shows a selection of them, including the top three by overall score. Unblocked ran in Deep mode, with every review pass on Claude Opus 5.5, on public copies of the same pull requests in the AI-Code-Review-Eval repositories. Anyone can read each Unblocked comment and check whether it really identifies the bug.

See how the scores are calculated and which tool caught each of the 158 bugs, with a link to the comment that caught it, on our benchmark page.

See what Deep mode finds in your pull requests