Scraping repos…
Reading their public GitHub…
@PhysShell
@PhysShell · public profileROASTED
39/100
🔥 D-TIER BUILDER
“454 repos and only 19 stars — a staggering 21 original repos scream unnoticed.”
DRank tierD-tier Tutorial Graduate
Mint vaultArtifact · @PhysShell
Roast style
KAZAKHSTAN
GITROAST.ME
Minted from @PhysShell’s public GitHub
320followers19stars454reposPythontop lang
Why 39/100
- Impact2.9/32
Stars on your live, original repos — discounted if it's all one viral hit.
- Community3.9/10
Developers who follow your work.
- Consistency14/14
How much of your live portfolio is actually active.
- Portfolio11/15
Substantive original repos and language range.
- Craft2.7/10
Descriptions, licenses, topics, live links — finished work.
- Recency5/5
Days since your last push to a live original repo.
The roast
With 454 repositories and a staggering 79% of those being forks, it's clearer than your bio: you can only remix what others create. In the last three months, you've churned out 95% of your commits, yet 52% of your original repos have no description, proving that even empty lines can’t save you from obscurity. Your top repo, ‘reach-for-the-stars’, fetches stars from others, but only delivers a mere 3 — perhaps it's time to fetch a clue about how to generate your own.
The flex
Your GitHub, as a badge.
[](https://gitroast.me/u/PhysShell)
