What this probe helps you decide
Whether a public repository's visible popularity/support signal is aligned enough with surrounding public evidence to trust, explain, or investigate further.
Best lifecycle moment
Public repo credibility / popularity context, before citing popularity as evidence of support.
What you submit
One public GitHub repository and the decision you need the popularity/support evidence to inform.
What product or surface this targets
Tell us the product, service, feature, SDK, app, workflow, dependency choice, AI-generated slice, or legacy module inside the repo/project that the probe should focus on. The repo is evidence; it is not automatically the whole target.
What we inspect
Visible GitHub popularity/support signals, surrounding public project evidence, support/gap observations, and boundary conditions.
What the report returns
CA$250 buys one public repo popularity/support context report with evidence summary, boundary notes, and next safe move.
Sample report / example
See the Star Support Probe sample.
What this does not include
- Private repository review
- Platform enforcement
- Full due diligence
- Security audit
Boundary of claim
This report does not determine whether stars are artificial, purchased, automated, fraudulent, bot-driven, scam-related, or owner-intent related. It compares visible popularity to surrounding public evidence.
Best-fit examples
- Public GitHub repo with a visible popularity signal.
- Maintainer or buyer preparing a public evidence explanation.
- Dependency review where popularity needs context.