Scraping repos…
Reading their public GitHub…
🔥 CERTIFIED DISASTER
“28 repos with 0 stars and a D-tier Builder Score — the epitome of dead weight.”
Tap the card to see how it was minted
Minted from @Jlvieira0909’s public GitHub
12followers0stars28reposTypeScripttop lang
Why 32/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
Your GitHub screams 'abandoned' louder than a gym_project that died two weeks after birth. With 93% of your 28 repos lacking descriptions and your best effort hitting a total of 0 stars, it's clear your coding experience isn’t even worth a thumb's up. If commitment issues were a repo, the vfr-catalog and WebPokedex would lead the charge — both projects lifeless, kept under 20 KB and far too casual to make noise in the dev community.
Your push cadence could serve as a case study in procrastination: the longest gap between repo updates spans 136 days, and half your projects sit untouched in a void. You’ve collected enough repos to fill a portfolio, yet they sit like trophies without pride or purpose. At this point, you've mastered the art of maintaining an empty legacy, with every empty repo a testament to inertia — a perfect D-tier score for a tutorial graduate stuck in a loop of drafting illusions without execution.
[](https://gitroast.me/u/Jlvieira0909)Account age, portfolio size, public repo count.
Builder Score recalibrated 2026-07.