How We Score
One question, one number.
What we judge
Sorcade cares about one thing: is this game fun to play? Being open source is the entry requirement, not a bonus. GitHub stars, code quality and commit activity are not part of the score.
One score, 0–100
Every game gets a single whole-number score from 0 to 100. A score may come with a one-line verdict or a longer write-up, but it doesn't have to. When forming a score we consider, among other things:
- Gameplay — is the core loop fun, deep and satisfying?
- Completeness — can you finish it or play it for a long time, or is it missing key parts?
- Presentation — art direction, readability, animation, music and sound.
- Getting started — how easy is it to get, install and learn?
- Technical quality — stability, performance, saves and platform support.
These are guidelines, not separate sub-scores.
What the numbers mean
| 90 –100 | 必携の名作 |
| 75 – 89 | 強くおすすめ |
| 60 – 74 | 試す価値あり |
| 40 – 59 | 賛否両論 |
| 0 – 39 | おすすめしない |
Games we haven't scored yet are shown as TBD. We never guess a score from stars or other data.
Independence
- Sorcade never accepts payment for a score, a better score or placement.
- Developers can't preview or approve scores.
- Team members with a conflict of interest (for example, they contributed to the game) don't score it, or the conflict is disclosed.
- Any future sponsorship will be clearly labeled and kept separate from scores.
Updates
Open-source games change often. We may re-score a game after a major update; the date shown is the date of the latest score.
Use of AI
Game data is collected automatically from GitHub's public API, and the site is maintained with AI assistance. Some game descriptions and translations are written with AI assistance and labeled as such. Scores are always given by people on the Sorcade team.
User Score
The User Score is the average of the scores players submit. It's shown once a game has at least 5 player ratings. It is completely separate from the Sorcade Score.
Corrections and replies
If something we wrote is factually wrong, we'll fix it and note the date. Opinions won't be changed on request, but developers can send a written reply through our reply process.