Scraping repos…
Reading their public GitHub…
🔥 CERTIFIED DISASTER
“4 repos under 20 KB and 53% of your code has no description? Yikes.”
Tap the card to see how it was minted
Minted from @gianzav’s public GitHub
8followers13stars26reposPythontop lang
Why 30/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 have 26 repos and somehow only managed to squeeze out 13 stars, which is a real feat in mediocrity. Your repo 'aspbox' came in at a titanic 18 KB — barely enough to justify its existence. A staggering 53% of your original repos have no description, leaving potential users more confused than inspired.
You created 8 projects but abandoned them within two weeks, not even letting them breathe before ghosting them. The push cadence is tragic; the longest gap was 452 days, while only 11% of your repos saw action in the last 90 days. With a Builder Score of 30/100, you’re residing in the D-tier, where enthusiasm doesn’t quite translate into productivity.
[](https://gitroast.me/u/gianzav)Account age, portfolio size, public repo count.
Builder Score recalibrated 2026-07.