GitHub fake engagement detection tool
Built for Open-source project maintainers concerned about fraudulent GitHub stars and engagement metrics..
“## Fake Engagement Alert for `Panniantong/Agent-Reach` [phantomstars](https://github.com/tg12/phantomstars) has detected a likely fake star/fork campaign targe…”
The receipts — real demand
“## Fake Engagement Alert for `Panniantong/Agent-Reach` [phantomstars](https://github.com/tg12/phantomstars) has detected a likely fake star/fork campaign targeting this repository. **Scan date:** 2026-06-09 ### Summary | Metric | Value | |--------|-------| | Engagers scanned (24 h window) | 296 | | Likely fake | **12** (4.1%) | | Suspicious | 67 | | Previously seen likely fake | 1 (0.3%) | | Repeat offenders | 0 …”
Full dossier
Unlock the full dossier — free
Every corroborating quote, the source receipts, and the community echo. One email, no payment.
Why this is a gap
Surfaced from a high-intensity complaint with clear willingness to pay and a specific, reachable audience.
The market
Open-source maintainers concerned about fraudulent GitHub stars and engagement. No search volume provided; the pain shows real instances of fake campaigns, but the audience is niche (maintainers of popular repos).
Competition & the opening
Phantomstars and a few other detection tools exist; GitHub's own detection is opaque. The gap is a transparent, accessible tool for maintainers to audit engagement and get alerts.
What's hard to build
GitHub's API is rate-limited and detection requires behavioral analysis (timing, geographic clustering, account age patterns). Building reliable heuristics that avoid false positives while catching sophisticated bot networks is genuinely hard without access to GitHub's internal data.
Why now
Bot-driven star/fork campaigns are proliferating as GitHub's native detection remains opaque and reactive.
How you'd monetize
$29/month SaaS per organization