Scraping repos…
Reading their public GitHub…
🔥 CERTIFIED MEDIOCRITY
“14 stars across 27 repos screams 'dormant developer' hard.”
Tap the card to see how it was minted
Minted from @spmzt’s public GitHub
30followers14stars45reposCtop lang
Why 41/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 27 original repos yet managed only 14 stars — that’s a serious lack of enthusiasm for your own work. Out of 45 repos, 10 are mere echoes, all under 20 KB without a single star, like ‘spmzt’ and ‘stayrtr’ — the ghosts of half-hearted efforts. Even ‘tcp_bbr’, your so-called pseudocode masterpiece, with a stellar lifespan of two weeks before vanishing, shows you can't commit to a decision or a function.
Your longest gap between pushes was a staggering 568 days, more than a year of silence, while 30% of your repos lay untouched over the last 90 days, echoing your productivity mantra: 'Why code when you can procrastinate?' With eight different languages stuffing your repos yet only a few stars to show, it feels like you were just throwing darts in the dark. Pouria, it’s clear you’re far more comfortable as a FreeBSD shadow than as an actual developer.
In the end, your 41/100 Builder Score is a fitting representation: just shy of C-tier mediocrity, and showing more ambition to fork than to finish. If only you invested as much energy in your original work as you do collecting repo ghosts, you might still be relevant in the dev world.
[](https://gitroast.me/u/spmzt)Account age, portfolio size, public repo count.
Builder Score recalibrated 2026-07.