Scraping repos…
Reading their public GitHub…
🔥 CERTIFIED DISASTER
“328 repos and 0 archived — welcome to the graveyard of abandoned dreams.”
Tap the card to see how it was minted
Minted from @bradtraversy’s public GitHub
76Kfollowers148Kstars328reposJavaScripttop lang
Why 98/100
Stars on your live, original repos — discounted if it's all one viral hit.
Gated: only opens past 75k effective stars AND 10k followers.
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.
The roast
You’ve got 25 repos that died within two weeks, like astro-blog or htmx-crash-course, then went silent for over six months. The naming crimes on proshop-v2 are almost as embarrassing as the 119-day push gap between commits. Open issues are piling high in your projects: 115 on electron-course-files alone, and yet no repos are marked as archived. You've mastered the art of pumping out noise, but it's clear you're just killing time with 0 repos actually maintained.
[](https://gitroast.me/u/bradtraversy)Days since your last push to a live original repo.
Account age, portfolio size, public repo count.
Builder Score recalibrated 2026-07.