The problem
"Is this ready to ship?" gets answered by vibes, or by a senior engineer spending an afternoon reading a repo. Neither scales, and neither leaves a record you can compare against next month.
Scores how production-ready a repo actually is, and shows its work.
"Is this ready to ship?" gets answered by vibes, or by a senior engineer spending an afternoon reading a repo. Neither scales, and neither leaves a record you can compare against next month.
Make it mechanical. Analyze repo structure, deployment configuration, and engineering standards through the GitHub API, and produce a score with the reasoning attached rather than a bare number.
Any score invites gaming, and this one can't see whether the code is good — only whether the scaffolding around it exists. A repo can pass with tests that assert nothing. I kept every check and its reasoning visible so it reads as a checklist to work through, not a verdict to trust.
Point it at a repo and get a readable readiness breakdown, with history tracking so you can watch a project's score move as you fix what it flagged.
05 Built with
06 Screens