Scraping repos…
Reading their public GitHub…
🔥 CERTIFIED DISASTER
“One star for 16 repos, and that’s generous for copy-paste projects.”
Tap the card to see how it was minted
Minted from @doaoww’s public GitHub
1followers1stars17reposTypeScripttop lang
Why 25/100
Stars on your live, original repos — discounted if it's all one viral hit.
Developers who follow your work.
How much of your live portfolio is actually active.
Substantive original repos and language range.
Descriptions, licenses, topics, live links — finished work.
Days since your last push to a live original repo.
The roast
You’ve got 17 repos, and somehow only one managed to scrape a single star. Exactly zero of your 16 original repos have descriptions, making it a guessing game for anyone brave enough to browse. The crown jewel here, 'my-test-project', is the poster child for uninspired naming — a project that screams ‘I couldn't be arsed.’
Dead on arrival — ‘Sana’ was created and abandoned within two weeks, collecting dust for over six months now. You maintain 53 runtime dependencies in 'micro-lender-ai', so the only thing micro here is your ability to curate a clean project. With a long push gap of 36 days between your repo updates, it's no wonder your GitHub Builder Score lands at a dismal 25/100 — it's clear you’re still learning how to spell 'commit'.
[](https://gitroast.me/u/doaoww)Account age, portfolio size, public repo count.
Builder Score recalibrated 2026-07.