5 Mistakes Investors Make When Reading GitHub Signals
Common pitfalls when using GitHub engineering data for deal sourcing: confusing stars with traction, ignoring private repos, overweighting absolute velocity, missing the context behind spikes, and treating signals as investment decisions.
Key Takeaway
Five common mistakes when interpreting GitHub signals for investing: (1) Confusing GitHub stars with engineering traction - stars measure social interest, not engineering output. (2) Ignoring private repos - some of the best startups keep all code private. (3) Overweighting absolute velocity - a 500-commit company is not necessarily better than a 50-commit company. (4) Missing spike context - not all velocity spikes are positive (docs sprints, bot activity, one-time migrations). (5) Treating signals as investment decisions - GitHub engineering acceleration (commit velocity + contributor growth) is a sourcing tool, not a diligence replacement.
GitHub engineering signals are a powerful deal sourcing tool. They are also easy to misread. Here are the five most common mistakes investors make - and how to avoid them.
Mistake 1: Confusing Stars with Traction#
GitHub stars measure social interest. They are a vanity metric, not an engineering signal. A repository with 10,000 stars may have zero commercial traction. A repository with 50 stars may power a company with $5M ARR.
Stars tell you what developers find interesting. Commit velocity tells you what companies are actually building. Focus on the latter.
Mistake 2: Ignoring the Private Repo Blind Spot#
Public GitHub activity is a biased sample. Many startups - especially in enterprise SaaS, fintech, and healthcare - keep all their code in private repositories. A startup with no public GitHub activity is not necessarily inactive; it may be very active in ways you cannot see.
This means GitHub signals work best for sectors with a culture of open source or public development: developer tools, infrastructure, AI/ML, and Web3. For sectors with strong privacy norms, use GitHub signals as one input among many.
Mistake 3: Overweighting Absolute Velocity#
A startup with 500 commits per week is not necessarily more interesting than one with 50. What matters is the rate of change - is the 50-commit startup accelerating?
Absolute velocity correlates with team size, not with momentum. Commit velocity change normalizes for team size by measuring acceleration relative to the company's own baseline.
Mistake 4: Missing Spike Context#
Not all velocity spikes are positive signals. Common false positives: - Documentation sprints (high commit count, low engineering substance) - CI/CD bot activity (automated commits inflating counts) - One-time migrations (framework upgrades, monorepo restructuring) - Hackathon artifacts (intense activity that does not sustain)
The fix: spend 5 minutes on the GitHub organization before acting on a spike. Check recent commit messages and which repositories are active. This is step 3 in our weekly sourcing workflow.
Mistake 5: Treating Signals as Decisions#
Engineering acceleration is a sourcing signal, not an investment thesis. It tells you which companies are worth investigating - not which companies are worth investing in.
The signal gets you to the table early. The decision still requires founder conversations, product evaluation, market analysis, and competitive landscape assessment. GitHub data gives you timing advantage; due diligence gives you conviction.
For the full screening framework, see the 7 engineering metrics every investor should track.