Real runs of free repos, recorded by the people who ran them

What are you trying to build?

Ask in plain words. Answers draw on founder-tested records; browse every record below.

RepoVerifier is thinking…

1 free conversation, no signup required.

Latest records

Recently tested

All reviews →
Solid 3900 stars

conorbronsdon/avoid-ai-writing, Solid, tested by @balajiloganathan

Claim: Unlike most agent-skill repos, this one ships a real, zero-dependency detection engine alongside the prompt, with a genuine regression-tested suite (150+ tests, many tied to real GitHub issue numbers) and a self-published PROOF.md that reports its own false-positive research — including a paragraph-level ROC-AUC of 0.501, a coin flip, disclosed without being asked.

Tested by @balajiloganathan Founder-tested 10 Sep 2026
Solid 32200 stars

tt-a1i/archify, Solid, tested by @balajiloganathan

Claim: Claims "proof, not promises." Fed it a novel scenario and it flagged an unresolved design detail instead of inventing an answer. The installer is pushy though.

Tested by @balajiloganathan Founder-tested 03 Sep 2026
Solid 710 stars

StJudeWasHere/seonaut, Solid, tested by @balajiloganathan

Claim: Claims to be an open-source SEO audit tool. We pointed it at our own site and it caught a real broken link we had missed, with zero false critical alarms.

Tested by @balajiloganathan Founder-tested 21 Jun 2026

25 reviews so far — 23 solid, 1 partial, 1 overhyped.

The process

How a repo gets tested

Every record starts with a person running a free repo on their own machine. Nothing is published until an editor has approved it.

  1. 01

    Submit

    Run the repo yourself, then send the claim you tested, your scores, your setup and your evidence.

    You
  2. 02

    AI triage

    An automated check compares your notes with the README and flags gaps. It does not decide.

    Automated
  3. 03

    Editor review

    A person reviews the submission and approves, asks for changes, or declines with a reason.

    Editor
  4. 04

    Tested

    The record goes live: Tested by @you. Reviewed by RepoVerifier.

    Published
  5. 05

    Certificate

    You get a Testing Certificate or Testing Record page and a README badge to share.

    Yours to share

Evidence is human-reviewed, not independently execution-verified. One run, on one machine, by the tester named on the record.

On every record

What you get

  1. A verdictHidden Gem, Solid, Partial, Overhyped or Dangerous, always written out.
  2. Five scoresInstall, docs, whether the claim held, setup ease and real-world use, each out of 5.
  3. The setup it ran onOS, runtime and version as the tester listed them, so you can compare with your own machine.
  4. A README badgeFor maintainers. It links back to the full record.
Community-tested

Run by the tester named on the record. An editor approves it before it is published.

Founder-tested

Run by the founder of RepoVerifier, under the same evidence standard and the same editorial check.

Tried a free repo? Record it.

If an editor approves it, your run becomes a public record with your handle on it, and a certificate you can share on LinkedIn or YouTube.

Become a tester