Scraping repos…
Reading their public GitHub…
🔥 D-TIER DISASTER
“39 repos, 6 stars, and somehow just as cool as a wet sock.”
Tap the card to see how it was minted
Minted from @tsanta22Kyle’s public GitHub
35followers6stars39reposJavatop lang
Why 27/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
Sitting on 39 repos but only managing 6 stars is truly an achievement in mediocrity. 26 of them are abandoned within weeks, ghosting GitHub like they had a bad date. Naming your project 'my-fishooo-ERP' is bold, in the same way a toddler’s crayon drawing is considered art. 78% of your repos skip descriptions entirely, making it less a portfolio and more a cryptic graveyard of bad ideas.
The vast iOS black hole of 5% push activity in the last 90 days bumps the 'vanity gap' into a chasm — 37 repos for 6 stars is a brag only you could think is cool. Let’s not forget those 13 lightweight repos under 20 KB, which should be classified as public notes rather than actual projects. The longest push gap of 133 days proves you've mastered the art of procrastination while showing off a diversity of languages like TypeScript and Java that get no real love — 4 stars out of 37 for TypeScript and absolute silence for Jupyter Notebook.
Overall, your GitHub reads like a sad echo of potential, with a Builder Score of 27/100 showing it wasn't just the projects that died, but the drive itself. A grand total of 0 Jupyter stars says it all, but hey, at least the names are catchy.
[](https://gitroast.me/u/tsanta22Kyle)Account age, portfolio size, public repo count.
Builder Score recalibrated 2026-07.