Scraping repos…
Reading their public GitHub…
🔥 TUTORIAL GRADUATE
“70 repos and 14 stars — a vanity graveyard rich in wasted space.”
Tap the card to see how it was minted
Minted from @azekowka’s public GitHub
50followers14stars70reposTypeScripttop lang
Why 39/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 crammed 70 repos into your account, yet only 14 stars to show for it, which screams 'abandon all hope'. 43 of those repos were dead on arrival, conjured and forgotten within two weeks, like a rogue wave of coding enthusiasm that never learned to swim. The commitment level is abysmal; over 33 repos untouched for more than a year signals a classic case of project commitment issues, reinforced by commit messages that are more ghostly than substantial, with 35% of them lacking a single coherent description.
Let’s talk about naming crimes. Repos like 'bzfar-clone' and 'telegram-clone' aren't just uninspired — they showcase a persistence in mediocrity that's almost admirable. Your stubborn choice of having 50 runtime dependencies in 'bzfar-clone' reads like a desperate cry for help from a cargo-cult coder. With a Builder Score of 39/100, it's clear that the only thing busier than your repo count is your ability to ignore them, proving quantity will never trump quality in this vanity graveyard.
[](https://gitroast.me/u/azekowka)Account age, portfolio size, public repo count.
Builder Score recalibrated 2026-07.