About
Codeforces Community Rating ranks Codeforces users who passed community review.
Codeforces does not run the project. It is made by Christine- and a group of admins with the community's help.
Project goals and principles
The goal is a community overwatch system for Codeforces. Cheating kills the sport when results stop feeling trustworthy.
- Maintain sportsmanship among users who respect the game.
- Value transparency, but do not publish details that help cheaters.
- Rely on the community: experienced community members conduct reviews; users can report later evidence.
Final statuses
The review system ends with one of three public statuses.
| Final status | Meaning |
|---|---|
| clear | Review reached clearance, so the user appears in the project ranking. Clear status can change after later cheating or missed evidence. |
| uncertain | Review did not clear the user. There may be cheating evidence, but reviewers did not agree enough under the rules to close the case as cheater. |
| cheater | The user has a project cheating finding or an external cheater database match. The user is not included in the project ranking. |
Statuses are not permanent. New evidence or later review can change them.
Admins can set statuses without a review case. The decision source is public and appears in Lookup.
Limitations of the project
- Clearance does not prove that a user has never cheated or will never cheat in the future.
- False negatives can happen: a user who cheated may still be marked clear if review misses evidence.
- False positives can happen: a user who did not cheat may still be marked cheater if evidence is misleading.
Users whose last decision was uncertain or cheater can reappeal once through Apply.
How reviews and reports work
| Part | What it means |
|---|---|
| status | A user's status can come from reviewer votes, an admin decision, or an outside cheater list. Handles on that outside list are not sent to reviewers. |
| admin decisions | Admins can grant member and reviewer rights when they have enough Codeforces community context. |
| review cases | Reviews cover applications, nominations, reappeals, and admin-opened cases. Reviewers get assigned sampled cases. |
| reports | Reports are private evidence. Report reviewers decide whether the target is clear, cheater, or there is not enough evidence. |
| after a clear report | Clearing a report is not enough by itself. The target still needs to pass eligibility before entering the ranking. Failed checks mean not eligible; external cheater database matches still mean cheater. |
| nominations | Reviewer or admin nominators may cast one vote on the case they opened. Ordinary member nominators cannot vote. Report reviewers see the target and evidence, not reporter history. More rules are on the Reporting page. |
Public features
| Ranking | Clear users. |
|---|---|
| Contests | Clear-user contest standings. |
| Community | Members, reviewers, and admins. |
| Nominate | Member nominations for first-time review. Reviewer or admin nominators can cast one vote. |
| Uncertain | Users whose review ended without clearance and without closing as cheater. |
| Cheaters | Project cheating findings and external cheater database matches. |
| Report | Private reports from users. Report reviewers can see evidence on assigned report cases. |
| Lookup | Status, decision source, rating, roles, and known handles. |