1,000 Repos Under 1,000 Stars

one thousand.

that's the official shape of undrdr: 1,000 open source repos under 1,000 stars. not 1,001. not an infinite feed. the list gets updated, refreshed, and pruned, but it never grows past the cap.

nobody asked me to do this. there's no business model. no vc pitch. i just kept finding incredible work buried under the algorithm's preference for things that are already popular, and it started to feel criminal not to organize it.

so i built undrdr. and here's what a year of staring at the long tail of open source taught me.

stars are a garbage metric

here's the number that broke my brain: most useful software still lives far below the visibility line. many of the best repos in undrdr have under 50 stars. plenty have under 100. stars measure distribution, not usefulness.

fifty-nine stars. that's it. that's the "middle" of open source quality.

and yet — some of the most inventive, well-architected, genuinely useful code i've ever seen lives in that under-50 bucket. mcp servers that wire ai agents into your workflow. swift tools that do one thing perfectly. rust crates that solve problems you didn't know you had.

the repo with 3,000 stars? probably a todo app tutorial. the repo with 12 stars? probably a security auditor that actually works. stars measure distribution, not quality. they measure marketing budgets, not engineering. they measure "found product-market fit," not "solved a real problem."

i stopped caring about stars around week three. what i care about now is: does this solve something? is the code honest? would i use it?

the mac is quietly eating everything

the mac-native corner keeps showing up. swift projects, menu bar tools, local-first utilities, tiny automation apps. not because they're trendy, but because people building for their own machines tend to solve concrete problems.

the narrative says the future is web-first. the data says otherwise. there's an entire ecosystem of people building native mac tools — menu bar apps, cli utilities, system-level integrations — and almost none of them get the attention they deserve.

the biggest category? "mac tool" with 124 repos. that's not a coincidence. apple silicon changed the game, and a generation of developers who actually use their machines (instead of just deploying to them) are building for it.

the second biggest? "mcp server" with 63 repos. model context protocol is less than a year old and it's already the nervous system of the agent ecosystem. six months ago, nobody knew what it was. now it's the standard for how ai tools talk to the world.

what gets ignored (and why)

the pattern is consistent. repos get ignored when:

• they solve a problem developers have but don't talk about (dependency auditing, log parsing, config management)
• they're written for a platform that tech twitter doesn't use (macos, linux desktop, self-hosted)
• they do one thing well instead of ten things poorly
• the readme is bad (this is the biggest one — great code, terrible marketing)

the last point is the tragic one. i've lost count of how many repos i found where the code was exceptional but the readme was two sentences and a broken badge. if you can't explain what your thing does in ten seconds, it doesn't matter how good it is. that's not fair. but it's how it works.

the ones that changed me

i didn't just curate undrdr. i used it. and some of these repos genuinely changed how i work:

mcp servers that let my agents talk to databases, filesystems, and apis without me writing glue code. that shifted my entire architecture from "build the integration" to "wire the protocol."

a cli tool that does one thing — sanitizes my clipboard — and does it so well i forgot it's there. that reminded me what software is supposed to feel like.

a rust-based search tool that's faster than anything i've used. it made me realize that "fast enough" is never fast enough. there's always room for a rewrite in rust.

these aren't the repos with the most stars. they're the ones that made me stop scrolling and start building.

why i keep going

every week i run the generator. it scans github with a mix of queries — topics, languages, organizations. it pulls candidates, filters out forks and archived projects, checks star counts, and queues the ones that fit.

then i look at every single one.

that's the part that scale can't replicate. curation isn't filtering. it's judgment. it's looking at a repo and knowing: this matters. not because it's popular, but because someone sat down and solved a real problem in a real way, and the only thing standing between them and the people who need it is an algorithm that prefers things that are already seen.

undrdr is my way of fighting that. 1,000 repos under 1,000 stars, always refreshed, never inflated.

if you take one thing from this

next time you're searching for a tool, sort by "recently updated" instead of "most stars." scroll past the first page. look at the repos with 12 stars and a README that actually explains what it does.

you'll find better software. i guarantee it.

and if you find something good — the kind of repo that makes you go "how does nobody know about this?" — send it my way. undrdr/submit. i'll check it. if it fits, it goes in.

written after running the weekly undrdr generator at 2 am. 1,000 repos under 1,000 stars, and the cap stays sacred.