BeforeVC
All articles
githubstartup signalsopen source

Can GitHub Stars Predict Startup Success? What the Data Shows

GitHub stars get dismissed as vanity metrics. But for angel investors who know how to read them, star patterns reveal something real about startup trajectory.

March 6, 2026 · 6 min read

Can GitHub Stars Predict Startup Success? What the Data Shows

The Metric Everyone Dismisses and Nobody Stops Watching

GitHub stars get written off constantly. "Vanity metric," investors say, right before asking a founder how many stars their repo has. The dismissal is partly deserved. A repo can accumulate 10,000 stars from a single Hacker News thread and then flatline forever. That's noise.

But strip out the noise and there's something real here. The question worth asking isn't whether github stars predict startup success in isolation. It's whether star patterns carry signal that other early-stage data doesn't. Based on what we've seen across hundreds of open source startups, the answer is yes, with important caveats.

Star Count Is the Least Interesting Number

If you're looking at total star count, you're already doing it wrong.

Supabase crossed 100K GitHub stars before its Series B. Impressive, sure. But the investors who made money on Supabase weren't the ones who noticed the 100K milestone. They were watching in late 2020 and early 2021, when the repo was growing at 2-3% week over week, consistently, for months. That sustained acceleration is a different signal entirely.

Star velocity is what matters. Specifically, these three patterns tend to precede breakout outcomes:

Steady weekly growth over 12+ weeks. A repo that gains 200-400 stars per week for three months has real organic distribution. Developers found it, used it, and told other developers. That's a distribution channel, not a popularity contest.

High star-to-fork ratios. Stars with proportionally high fork counts suggest the project is being actively used, not just bookmarked. A ratio of roughly 10:1 stars to forks is typical. Projects with 5:1 or lower are getting cloned constantly. That's usage data.

Spike recovery. A repo that spikes from a press mention and then holds most of those stars is structurally stronger than one that spikes and reverts. The hold rate after a spike tells you how many of those new visitors actually found something worth starring.

What the Data Shows Across Open Source Startups

Several researchers have tried to correlate GitHub activity with funding outcomes. The findings are messy but directional.

A 2022 study of Y Combinator-backed startups with open source components found that repos in the top quartile of star velocity at the time of YC application were 2.4x more likely to raise a Series A within 24 months than those in the bottom quartile. Star velocity was a stronger predictor than total star count, commit frequency, or contributor count.

Correlation, not causation. High star velocity is partly a proxy for founder hustle (good at distribution), partly a proxy for market timing (built something people needed right now), and partly a proxy for product quality (kept those users engaged enough to star and fork). All three of those things predict startup success independently. That's why the correlation shows up.

The counterexamples are real too. Redis has been one of the most starred database repos for a decade. That didn't save its original company, Redis Labs, from the rough commercial path that eventually led to a rebrand and pivot. A great open source project and a great business are different things, and star counts alone can't tell you which one you're looking at.

What Stars Don't Tell You

Stars say nothing about revenue. Nothing about retention. Nothing about whether the founder can sell to an enterprise procurement team or build a support organization.

They also don't tell you about the founder's cap table, their previous exits, or whether they've already raised a seed round from someone who will make your follow-on complicated. Basic stuff, but GitHub stars will not surface it.

The other blind spot: stars from the wrong audience. A developer tool can accumulate enormous GitHub followings from hobbyists and students who will never pay for anything. If the target customer is a VP of Engineering at a 500-person company, student stars are close to worthless. You need to cross-reference star demographics with where the community discussion is actually happening, whether that's professional Slack groups, practitioner forums, or enterprise procurement communities.

The Right Way to Use This Signal

Stars are a screening tool, not a decision tool. Here's a practical framework.

Set a velocity threshold for initial attention: repos gaining 150+ stars per week for at least 6 consecutive weeks are worth a closer look. That's a rough filter that eliminates the noise without missing too many real signals.

Once something clears that bar, look at three things in sequence. First, contributor concentration: if 90% of commits come from one person, you don't have a project, you have a solo developer with an audience. Second, issue quality: read the open issues. Are they feature requests from serious users, or bug reports from people who installed it once and moved on? Third, the commercial overlay: is there a .com, a pricing page, a waitlist? Founders building toward a business signal it early.

The startups worth tracking are the ones where star velocity is accelerating and there's early commercial intent and the issue tracker shows engaged, sophisticated users. All three together is rare. When you see it, pay attention.

Where This Fits in a Broader Deal Flow Process

GitHub signals work best as part of a stack. Stars plus product launches (Product Hunt, Hacker News Show HN) plus job posting velocity plus founder background gives you a multi-dimensional picture that's much harder to fake than any single signal.

A repo can buy stars. It can time a Product Hunt launch. It's much harder to simultaneously manufacture accelerating GitHub momentum, a strong Show HN reception, a first job posting for a head of sales, and a founder who previously worked at Stripe or Databricks. When those signals converge, you're usually looking at something real.

The angel investors who consistently see good deals early aren't necessarily smarter. They've just built better signal systems and they check them consistently. (We wrote a full breakdown of 7 free deal flow tools for angel investors if you want to see what that stack looks like.)

That's the whole idea behind the beforeVC weekly briefing: surface the repos, launches, and founder moves that fit this multi-signal pattern before they're obvious. If you want that in your inbox every week, subscribe at beforevc.com.

Get the signal before the noise

Each week we scan thousands of signals and surface the highest-momentum projects. Five emerging signals, ranked and scored. Read in under 2 minutes.

Free weekly briefing. No spam, unsubscribe anytime.