Scraping repos…
Reading their public GitHub…
🔥 NAMELESS DISASTER
“Over a decade and 993 repos, still can't name a single one correctly.”
Tap the card to see how it was minted
Minted from @simonw’s public GitHub
17Kfollowers41Kstars993reposPythontop lang
Why 79/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
All those years and you're still naming repos like a toddler: "simonwillisonblog-backup" and "datasette-backup"? Is this a codebase or an online storage bin? You’ve muscled together 99 repos with zero stars and near-empty datasets - 'datasette-allow-permissions-debug' clocks in under 20 KB. Nice graveyard too; two archived repos, but that’s only for the strong winds of your creativity blowing them away.
With 35214 stars in Python and only 9 languages across your 92 original repos, your coding buffet looks more like a fast food menu. Sure, 87% of your repos saw action in the last 90 days, but that just shows how much you love pissing into a windstorm. Two archived projects can’t hide the fact that your repo naming skills freeze like your push cadence – longest push gap at 14 days suggests you’re saving all the magic for the grand reveal three months down the line. The truth is, 993 repos and you still can’t find the right name out of a hat.
Good luck turning "simonwillisonblog-backup" into your 994th star project; considering the coding octathlon you’ve completed, it’ll be near impossible to even hit 20 stars on that one, buddy.
[](https://gitroast.me/u/simonw)Account age, portfolio size, public repo count.
Builder Score recalibrated 2026-07.