Scraping repos…
Reading their public GitHub…
Abdulaziz Gabitov
@azekowka · public profileROASTED
37/100
🔥 D-TIER DISASTER
“55 repos and only 15 stars — a vanity project with a Github graveyard.”
DRank tierD-tier Tutorial Graduate
Mint vaultArtifact · @azekowka
Roast style
CHINA
GITROAST.ME
Minted from @azekowka’s public GitHub
53followers15stars71reposTypeScripttop lang
Why 37/100
- Impact2.6/32
Stars on your live, original repos — discounted if it's all one viral hit.
- Community2.4/10
Developers who follow your work.
- Consistency7.3/14
How much of your live portfolio is actually active.
- Portfolio12.1/15
Substantive original repos and language range.
- Craft3.7/10
Descriptions, licenses, topics, live links — finished work.
- Recency5/5
Days since your last push to a live original repo.
The roast
You’ve managed to create 55 original repos but only scraped together 15 stars, resulting in a stellar vanity metric of 27%. Forty-three of those repos were dead on arrival, abandoned within two weeks and now echoing in the void since you’ve gone silent for over six months. Your naming conventions often read like a bad episode of ‘GitHub For Dummies’ — 'bzfar-clone', 'telegram-clone', and incredibly vague 'project' speak volumes about your commitment to clarity.
With 35% of your original repos lacking any description and five primary languages spread across just 55 repos, it’s evident you lack focus. Your push cadence is a testament to this — 108 days of inactivity is sufficient time to forget your own code. Maybe those 50 runtime dependencies in your package.json file in bzfar-clone are weighing you down, much like the weight of a portfolio that dead ends before it starts.
The flex
Your GitHub, as a badge.
[](https://gitroast.me/u/azekowka)
