Tested records for free AI repos
Every record starts with a person running a free repo on their own machine. An editor reviews each submission before anything goes live, and the record names who tested it and what held up. No hype. Just what happened.
What we’ve built so far
25
Records published
6
Stacks
4
Use cases
repoverifier.dev runs on Railway with PostgreSQL and was built with Claude Code using ECC and gstack.
Three ways to use this site
How a record is made
- A person runs the repo on their own machine: the site’s founder (labeled Founder-tested) or a community member who tested it themselves (labeled Community-tested).
- They follow the README as written and test one specific claim the repo makes.
- They record what happened, including any errors, word for word.
- An automated check compares your notes with the README and flags gaps. It does not decide.
- An editor reviews the submission before anything goes live, and for the most serious verdicts tries to reproduce the finding. The editor can approve it, ask for changes, or decline it. Nothing is published automatically.
- The record goes live, reading “Tested by @handle. Reviewed by RepoVerifier.” It has its own page, a Testing Certificate (Hidden Gem, Solid, Partial) or a Testing Record (Overhyped, Dangerous), and a README badge the repo’s maintainers can add.
See the tested local AI stack →
What each record scores
Each record scores five things, from 0 to 5.
- Install works: 0 = would not install, 5 = installed first try.
- Docs accuracy: 0 = the docs contradict the code, 5 = every documented step worked.
- Claim held: 0 = the claim is false, 5 = the claim fully held.
- Setup ease: 0 = blocked by setup problems, 5 = no friction.
- Real-world utility: 0 = not useful, 5 = the tester would use it in production.
Some earlier records show “Scores not recorded for this run.”
Verdicts
HIDDEN GEM
Works better than claimed. Underrated.
SOLID
Does what it claims. Reliable.
PARTIAL
Some claims hold, with specific limitations recorded.
OVERHYPED
Claims more than it delivers.
DANGEROUS
Misleading claims, security risks, or could cause real harm.
Submitting and publishing a review is free. Payment, sponsorship, or any other consideration can never influence whether a submission is approved or what verdict it receives.
Common Questions
- How is a repo tested?
- Every tester, founder or community member, runs it on their own machine, follows the README as written, tests one claim and records what happened, errors included. Every record says it is one run, on one machine, by the tester named on it.
- Do you accept paid reviews or sponsorships?
- No. Submitting and publishing a review is free. Payment, sponsorship, or any other consideration can never influence whether a submission is approved or what verdict it receives.
- Can I add a record?
- Anyone aged 16 or older who has tested a public repo themselves can submit a record of it on the Join page. An editor reviews each submission before anything goes live. Submissions can be paused; the Join page says so when they are.