{"slug": "11-of-github-s-all-time-top-100-repos-passed-through-our-tracker-before-they-up", "title": "11 of GitHub's all-time top 100 repos passed through our tracker before they blew up. Here's what I learned.", "summary": "A developer tracking open-source AI projects since early 2025 found that 11 of GitHub's all-time top 100 repos passed through their tracker before reaching the top 100. The developer and a friend built Repository Radar, a curated list of notable repos, and observed that sustained project activity—not just star spikes—was a better predictor of long-term growth. They argue that the challenge in open source is no longer discovery but filtering the firehose of new projects.", "body_md": "I kept finding out about interesting open-source AI projects weeks after everyone else.\n\nSome tool would suddenly be everywhere on my timeline. I'd go look, and it already had 40k stars, a crowded issues tab, and five \"X but for Y\" projects built on top of it.\n\nI was always late.\n\nThe problem wasn't a lack of places to find new repos. It was the opposite.\n\n**AI open source has become a firehose.**\n\nNew agents, frameworks, runtimes, inference tools, databases, and developer primitives show up every day. GitHub Trending gives you a list. Hacker News gives you another. X gives you twenty more, usually with 🔥 somewhere in the post.\n\nThere is an absurd amount of good stuff being built. Keeping up with it is becoming a job.\n\nSo a friend and I started keeping our own list.\n\nThe rule was basically:\n\nIf we only had an hour this week to look at new open-source projects, which ones would we spend it on?\n\nThat list became a [biweekly writeup](https://repositoryradar.substack.com/). The writeup became a habit. And somewhere along the way, it became a dataset.\n\nSince early 2025, we've tracked 239 repos across 37 issues and recorded their GitHub metrics over time.\n\nWe call it [Repository Radar](https://repositoryradar.dev/).\n\nLooking back through that history, I started noticing a few patterns.\n\nWe track stars. Quite prominently, actually.\n\nNot because the repo with the most stars automatically wins, but because stars are a pretty good measure of where attention is moving.\n\nThe problem is that attention is noisy.\n\n**Most star spikes are noise.**\n\nA launch-day bump, a viral tweet, or a spot on a listicle can all produce a beautiful chart for a few days. Then nothing.\n\nThe repos that became interesting over time often had a different shape. The initial spike wasn't necessarily bigger. It just kept going.\n\nWeek two held up against week one. Sometimes it accelerated.\n\nSo the absolute star count became less interesting to me than the slope. And the slope became more interesting when I looked at what was happening underneath it.\n\nThis was probably the most boring pattern.\n\nReleases kept landing. Issues got closed. Contributor activity broadened beyond one person.\n\nThe repo was still visibly alive after the launch post disappeared from everyone's feed.\n\nThat's when a rising star curve became interesting.\n\n**Stars showed us where attention was moving. Project activity gave us a reason to keep watching.**\n\nNeither tells you whether a project is actually good. You still have to understand what the thing does.\n\nBut when you're trying to reduce a few thousand new repos to five worth opening, signals help.\n\nOf GitHub's current all-time top 100 repos, 11 passed through our radar before reaching the top 100.\n\nThat's not me claiming we can predict the future. We have missed plenty.\n\nBut it did make me think being early isn't entirely random.\n\nTake OpenClaw.\n\nWe first covered it at roughly 4k stars in January. Today it's north of 380k.\n\nAt 4k, it was still small enough to sit down, read through, and form an opinion.\n\nThe interesting part wasn't that 4,000 people had clicked the star button. The project was shipping. Attention kept growing. Contributor activity was expanding.\n\nIt later became our repo of the month. Twice.\n\n**By the time a project is everywhere on your timeline, discovering it isn't particularly difficult.**\n\nThe window I'm interested in is earlier, when the answer to \"does this matter?\" is still unclear.\n\nIn a good way.\n\nWriting software has never been cheaper.\n\nA weekend experiment can become a working repo. Internal tools get open-sourced. A researcher can turn a paper into something people can actually run. Small teams can ship projects that would have needed much larger teams a few years ago.\n\nMore things get built. More things get shared.\n\nI think that's great. But abundance cuts both ways.\n\n**The hard part is no longer finding open-source software. It's deciding what deserves your attention.**\n\nThat's the problem we've been trying to solve with [Repository Radar](https://repositoryradar.dev/).\n\nEvery two weeks, my co-author and I go through the open-source AI firehose and pick the handful of projects we think are actually worth looking at.\n\nNot 50 links. A small, opinionated selection.\n\nFor each repo, we explain what it is, why we found it interesting, and how to get started.\n\nThat's the [Repository Radar newsletter](https://repositoryradar.substack.com/).\n\nThe [Repository Radar site](https://repositoryradar.dev/) is the data layer behind the curation.\n\nIt contains every repo we've covered, with live GitHub metrics and historical context.\n\nYou can see which projects have moved most since we first found them, compare stars, forks, contributors, issues, PRs, releases, and activity, filter the archive, or export the underlying data as JSON.\n\n**If you want the curation, subscribe to the biweekly newsletter.**\n\n**If you want to explore the repos and data yourself, play with the tracker.**\n\nThe list is hand-curated. It's opinionated. We'll miss things.\n\nI'd still rather give you five repos we have a view on than generate another feed of 500 things that happen to be trending.\n\nIf you actively follow AI open source, how do you cut through the noise?\n\nAnd if you had a radar for open source, what signal would you want on it that we don't track today?\n\n**I'd love to steal your best idea.**\n\nAnd if there's a repo we completely slept on, please tell me. That's literally what the radar is for.", "url": "https://wpnews.pro/news/11-of-github-s-all-time-top-100-repos-passed-through-our-tracker-before-they-up", "canonical_source": "https://dev.to/ahk-dev/11-of-githubs-all-time-top-100-repos-passed-through-our-tracker-before-they-blew-up-heres-what-i-m4p", "published_at": "2026-07-08 16:21:44+00:00", "updated_at": "2026-07-08 16:41:30.800140+00:00", "lang": "en", "topics": ["developer-tools", "ai-tools"], "entities": ["GitHub", "Repository Radar", "OpenClaw"], "alternates": {"html": "https://wpnews.pro/news/11-of-github-s-all-time-top-100-repos-passed-through-our-tracker-before-they-up", "markdown": "https://wpnews.pro/news/11-of-github-s-all-time-top-100-repos-passed-through-our-tracker-before-they-up.md", "text": "https://wpnews.pro/news/11-of-github-s-all-time-top-100-repos-passed-through-our-tracker-before-they-up.txt", "jsonld": "https://wpnews.pro/news/11-of-github-s-all-time-top-100-repos-passed-through-our-tracker-before-they-up.jsonld"}}