Open Source Contribution Tracker for Dev Teams
The Opportunity
Spotted on Hacker News · March 24, 2026
Scans package.json/requirements.txt, builds dependency graph, identifies maintainer health signals (last commit, open PR backlog, single-maintainer risk), tracks team's OSS contributions over time. $10/seat/mo.
Niche but clear gap. TAM is eng-forward companies with OSS commitments. Nice-to-have not must-have — harder to convert to paid. Good as freemium OSS tool with paid enterprise tier.
Why these scores?
Demand (pain) scored 3/5 (strong) — how urgently people need a solution.
Willingness to pay scored 3/5 (strong) — evidence people would pay for this.
Market gap scored 4/5 (very high) — how underserved this space is.
Build effort scored 3/5 (strong) — feasibility for a solo builder or small team.
Real Demand Evidence
“My company says it supports open source. But we have no visibility into which packages we depend on, which maintainers are burnout risks, or which contributions we've made back. It's all vibes.”
Willingness to Pay
Engineering orgs paying $20-50/seat on GitHub, $15-30/seat on Snyk, $10-20/seat on Socket.dev for dependency health. OSS contribution tracking is a gap in all of them. $10-15/seat/mo.
Score Breakdown
10/15Existing Solutions
Snyk (security only), Socket.dev (supply chain security), FOSSA (license compliance). No tool tracking contribution reciprocity or maintainer burnout risk.
✦ No clear solution exists yet — this is a wide-open opportunity.