Submit a review

Tested a repo yourself? Add your evidence.

Step 1 of 4: The repo and its claim

The repo and its claim

A public GitHub repo, like https://github.com/owner/repo.

Paste one sentence exactly as it appears in the README. No quote marks, no added words.

Published on the record as the claim you tested.

Your connection to this repo (required)

We can't verify this. The editor sees it, and an undisclosed connection can get a review removed.

Your verdict

Which verdict fits what you found? (required)
Score each criterion from 0 to 5 (required)
Install works0 = would not install. 5 = installed first try.
Docs accuracy0 = docs contradict the code. 5 = every documented step worked.
Claim held0 = the claim is false. 5 = the claim fully held.
Setup ease0 = blocked by setup problems. 5 = no friction.
Real-world utility0 = not useful. 5 = I would use it in production.
Total0 of 25

Your evidence

Evidence links make approval faster. Without them, an editor may ask for changes.

A reproducible fork or branch is the strongest evidence. It is harder to fake than a screenshot.

Sent to the editor only. Not published.

Screenshots, terminal output or recordings hosted elsewhere (gist, imgur, loom).

Sent to the editor only. Not published.

Published as your observations. Leave out links you want kept private.

Include the commit or release you tested, plus OS, hardware and language versions. Published on the record.

Confirm and submit

Evidence is human-reviewed, not independently execution-verified.