Scraping repos…
Reading their public GitHub…
🔥 CERTIFIED DISASTER
“Two years in, and zero passion for anything but empty repos.”
Tap the card to see how it was minted
Minted from @l9kk’s public GitHub
28followers1stars21reposPythontop lang
Why 20/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 testament to abandonment. 14 repos created and ghosted in under two weeks, with five of them ghosting for over six months — ascii, it-park, recipe, terricon-valley, terricon-front; have you tried building anything or just collecting repos like Pokémon? You boast 94% of your 18 original repos with no description; it’s almost like you want them to go unnoticed.
One star across 18 repos is an achievement, just not a good one. It’s like showing up to a cook-off with a single overcooked egg. The commit messages in CRM-backend scream indifference — 30% of the last 30 clocking in under 10 characters and your best is just a pair of empty quotes. Those 184-day gaps between pushes could be the subject of a case study on disengagement, but we already know the conclusion: dead silence.
Your portfolio’s Builder Score reads like a failed experiment; D-tier “Tutorial Graduate” is all the proof we need. Two years in and all you’ve built is a graveyard of near-empty repos. You should probably consider taking a real shot at something before declaring everything else ‘finished’ — because right now, your GitHub says you’ve given up before even starting.
[](https://gitroast.me/u/l9kk)Account age, portfolio size, public repo count.
Builder Score recalibrated 2026-07.