Scraping repos…
Reading their public GitHub…
🔥 NAMING CRIMES
“14 years in and naming a repo 'eslint-node-test' is still the best you can do.”
Tap the card to see how it was minted
Minted from @sindresorhus’s public GitHub
85Kfollowers149Kstars1.1KreposJavaScripttop lang
Why 99/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 churned out 1,145 repos but managed to keep your creativity on life support with names like 'eslint-node-test'. With 67,850 stars in TypeScript, you'd think one of those would inspire some originality, but here we are. Your cadence is so consistent that the longest gap between pushes is just 3 days, making your commit history feel more like a factory line than a creative process.
Despite being a so-called menace to production, your graveyard boasts only 2 archived repos, which is a bizarre flex in a sea of mediocrity. It's almost impressive how 100% of your repos saw action in the last 90 days, yet the standout remains a glorified collection of essential TypeScript types in 'type-fest'. After 16.8 years, you’ve turned prolific production into a numbers game, not a commitment to creativity.
[](https://gitroast.me/u/sindresorhus)Days since your last push to a live original repo.
Account age, portfolio size, public repo count.
Builder Score recalibrated 2026-07.