Scraping repos…
Reading their public GitHub…
🔥 D-TIER CATASTROPHE
“Two stars in 42 repos is a truly masterful, borderline comedic failure.”
Tap the card to see how it was minted
Minted from @Kirirto-kun’s public GitHub
16followers2stars42reposTypeScripttop lang
Why 27/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
Your GitHub is a graveyard of 42 repos, crowned by 'fire_spread' at two stars and followed by ghost ships like 'sanduai_frontend' and 'kirirto-kun', both left to collect dust with zero stars. A staggering 92% of your original 38 repos are so light on detail, they’d make a README-less void proud. You've got repos that are dead on arrival, after being created and abandoned within two weeks — 'sh_tg_jafar' and 'fire_spread' included, with not a peep in over six months.
Your push cadence could rival a hibernating bear, with the longest absence stretching 97 days — no wonder just 5% of your repos saw action in the last 90 days. It's almost impressive how you managed to accumulate 10 near-empty repos under 20 KB, while somehow failing to snag a single star in your top languages, except for the pity pull on Jupyter Notebook. It’s clear, 'builder score 27/100' feels generous for the ghost town you’ve built here; have you considered rebranding to 'Tutorial Graduate in Doom' instead?
[](https://gitroast.me/u/Kirirto-kun)Account age, portfolio size, public repo count.
Builder Score recalibrated 2026-07.