Quick answer
Stars and forks are cheap signals; issues, discussions, and long threads are expensive signals - harder to fake, closer to pain. For commercial OSS, combine quantitative GitHub stats with qualitative reading and sentiment-aware triage.
Best for: vendors monetizing OSS cores with cloud or enterprise editions.
When stars mislead
- Influencer traffic spikes
- Example repos for courses
- One-off HN front page without retention
Sentiment surfaces
- GitHub Discussions (if enabled)
- Reddit maintainer AMAs
- Hacker News release threads
Using Needle
Aggregate search across GitHub and other communities in one workflow - see Search. Exports for deeper offline analysis are not on Solo per CAPABILITIES.EXPORT_RESULTS in plans.js.
Related reading
- Stack Overflow + GitHub product research
- Dev tool GTM GitHub issues
- Stack Overflow and GitHub product research