Scraping repos…
Reading their public GitHub…
🔥 NAMING DISASTER
“92 repos with names that sound like they were generated by a toddler.”
Tap the card to see how it was minted
Minted from @simonw’s public GitHub
17Kfollowers40Kstars992reposPythontop 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
Your naming crimes could earn you a GitHub red card, with gems like simonwillisonblog-backup and datasette-backup barely breaking the creativity scale. A near-empty repo, datasette-allow-permissions-debug, doesn’t scream competence at 20 KB. Your 1,000 public repos are like a buffet of half-baked ideas, with 10 primary languages across them — Python hogging 35,000 stars while the rest gather dust and shrimps.
You've pushed in the last 90 days, and 84% of your repos saw action, but 2 of your 992 are now happily archived — that's a hell of a lot of ambition for two repos that decided to call it quits. With 40,400 total stars, it's as if you’ve mastered the art of being a Serial Shipper yet still managed to keep the actual shipping stick to sub-par cargo. At 18.4 years and a Builder Score of 79, you’ve got the reach but the depth is still swimming in shallow waters.
[](https://gitroast.me/u/simonw)Account age, portfolio size, public repo count.
Builder Score recalibrated 2026-07.