~ / how-we-score
How we score software reviews
Every Sudo Review score is out of 10. It comes from the same three criteria for every tool, with the same weights: developer experience, speed and value. Here is exactly how the number is built, and what each review shows you so you can check it.
01 / The formula
Three criteria, one weighted score
Each tool gets a rating out of 10 for each criterion. The final score is a weighted average of the three:
score = (developer_experience × 0.4) + (speed × 0.3) + (value × 0.3)Scores can carry one decimal place, for example 9.4. The weights never change from one tool to the next, so a score on one review means the same thing as a score on another.
02 / The criteria
What each criterion covers
Developer experience (40%)
What it is like to actually work with the tool: getting it set up, how clear the docs are, how it behaves in day-to-day use, how it handles errors, and how well it fits into an existing workflow. It carries the most weight because it is the part you live with every day.
Speed (30%)
How quickly the tool gets the job done. That covers how fast it runs and how long it takes to go from installing it to getting a useful result.
Value (30%)
What you get for what you pay. Free tiers, pricing, one-time versus subscription costs, and what you give up by choosing it are all part of value. A free tool can still lose points here if it costs you in other ways.
03 / Worked example
How the maths works
Say a tool is rated 9 for developer experience, 7 for speed and 8 for value:
| Criterion | Rating | Weight | Points |
|---|---|---|---|
| Developer experience | 9 | 40% | 3.6 |
| Speed | 7 | 30% | 2.1 |
| Value | 8 | 30% | 2.4 |
| Score | 8.1 / 10 |
Example only. These numbers are made up to show the calculation and are not from a real review.
04 / Stars
How the stars map to the score
The star rating is the score divided by two. A 10 is five stars, an 8 is four stars. The number out of 10 is the exact score; the stars are a quick visual.
05 / What you see
What every full review shows you
A score is only useful if you can see where it came from. A full Sudo Review includes:
- Scorecard: the score out of 10 and the star rating.
- Verdict: the short answer, in a sentence or two.
- Tested on: the platform and setup we used, such as Windows, macOS, Android or Docker.
- Why not a 10: exactly where the points were lost.
- Best for and skip if: who should use it, and who should look elsewhere.
- How we tested: what we did, and just as important, what we did not test.
- Sources: links to the official docs, repositories and coverage we relied on.
- Video review: a full video alongside the written review.
06 / Disclosure
Affiliate links and our own tools
We earn commissions from some affiliate links. Affiliate links are labelled, and they never change a verdict.
Partner offers on our deals pages are labelled as partner offers. If we review a tool we built ourselves, the review says so clearly.
07 / Questions
Common questions
Is the score a simple average?
No. It is a weighted average. Developer experience counts for 40% of the score, speed and value for 30% each.
Why does a great tool still get an 8?
Every review has a “why not a 10” section that names exactly where the points went, so you can decide whether that weakness matters for you.
Can I ask you to review a tool?
Yes. Send it through the request form and tell us what you would use it for.