Farol
Shares rank 16 of 17 code review tools by recommenders
Shows a risk map of a pull request for approvers; deterministic and advisory, never blocks merges. Critics find the UI poor and the report longer than reading code.
Shows a risk map of a pull request for approvers; deterministic and advisory, never blocks merges. Critics find the UI poor and the report longer than reading code.
7 people gave an opinion
- recommend it
- 5
- criticize it
- 2
- approval share
- 71%
Recommended in 1 of 13 months
- November 2025: not recommended
- December 2025: not recommended
- January 2026: not recommended
- February 2026: not recommended
- March 2026: not recommended
- April 2026: not recommended
- May 2026: not recommended
- June 2026: not recommended
- July 2026: not recommended
- August 2026: not recommended
- September 2026: not recommended
- October 2026: recommended
- November 2026: not recommended (month in progress)
Why it doesn’t carry the badge
- 5 people recommend itNeeds 10 or more, not met.
- 2.5 recommenders for every criticNeeds 2 to 1 or better, met.
- Recommended in 1 of 13 monthsNeeds 4 or more, not met.
The same three rules apply to every product, and the badge can’t be bought. How the badge works
What people say about it
The reasons people give, with the number of comments that give each one. Open a reason to read what they said.
Why people recommend it
Each mark is one comment
Useful risk map for reviewers
“I like the concept, a risk map could be useful in some circumstances but I absolutely hate the UI design”
Comment from 25 Oct 2026 in “Show HN: Farol – A risk map of a pull request for the person who approves it” Deterministic, advisory, never blocks merges
“It's deterministic and informs only; it never blocks a merge.”
Comment from 25 Oct 2026 in “Show HN: Farol – A risk map of a pull request for the person who approves it”
Other code review tools people recommend
The four most recommended other code review tools, with the same counts for each, so you can compare like for like. The tick on each bar marks the 2 to 1 line the badge needs.
| Product | Recommend | Criticize | Approval | Months | Owned | Badge |
|---|---|---|---|---|---|---|
| GitHub Stacked PRs | 64 | 63 | 50% | 3 | — | — |
| Gerrit | 60 | 12 | 83% | 12 | — | Approved |
| Graphite code review | 52 | 16 | 76% | 9 | — | Approved |
| CodeRabbit | 34 | 32 | 52% | 11 | — | — |
| FarolThis page | 5 | 2 | 71% | 1 | — | — |
What people said
6 of the 7 comments that mention it, newest first. Each links to the original comment.
“If there's anything we still need a human for, it's assessing risk.”
“it's hard for me to imagine something made with so little taste can be any good”
“the backend demo report seems longer and more complex than just reading the code”
“the first lines suggested to look at were importing things. Exactly what I really don't need to be reviewing”
“I like the concept, a risk map could be useful in some circumstances but I absolutely hate the UI design”
“It's deterministic and informs only; it never blocks a merge.”
Counts come from 1,795,640 Hacker News comments, November 2025 to November 2026. How we count. Report a mistake.