What’s my repo worth?
That half-finished project has a number on it. Here it is.
Paste a public GitHub repo. You’ll get a readiness score out of 100, a suggested asking range, and the full breakdown of how we got there — free, no account, nothing to install.
We never download your code
This reads GitHub’s public API — the repo’s file listing and sizes, not its contents. No clone, no upload, no account, and nothing stored about your project. If you later decide to sell it, that’s when the real pipeline runs: a full scrub for secrets and personal data, then an exact valuation. Not before.
What it actually measures
No black box. Six signals, each scored 0–100 and weighted, then adjusted for how much demand its category is seeing. You see every component — including the ones that hurt.
- completeness
- Does it build and run — a manifest, a deploy config, real source files.
- code volume
- How much genuine work is in there: source files and rough lines of code.
- tests
- Whether anyone tested it. The single biggest separator between a toy and an asset.
- docs
- A README with substance, and a docs folder if there is one.
- polish
- CI, a license, typed code, contributor docs — signs it was cared for.
- cleanliness
- How clean the code is of secrets and personal data. Scored after a scrub.
Then what?
Nothing, if you like — the number is yours. But if it’s more than you expected, list it. Free to list, and Cinderella only earns when it sells. See how it works or what it costs.
