About RepoRadar
RepoRadar answers one question: should I depend on this GitHub repo? Paste owner/repo, a GitHub URL, or an npm: or pypi: name. You get a plain verdict (Healthy, Caution, At risk, Avoid, or Too new), the rules that fired with their evidence, and what would change the verdict.
Why it exists
Adoption decisions get made in a hurry. A repo can look alive from its star count while its only maintainer has stopped committing, its license changed last spring, or the project has moved somewhere else. Checking each of those by hand takes time, and most people skip it. RepoRadar runs the same checks every time, from public data, and shows its working.
What a verdict is, and is not
- A verdict is the result of fixed, published rules. The methodology page lists each rule and its threshold.
- A verdict is not a security audit, and it does not read a repo's code for bugs or malicious changes.
- A star count is not evidence of quality. Anyone can buy stars for any repo. When the star history shows unexplained bursts, we say so and show the numbers. We describe patterns in the data, never people's intent.
Independence
RepoRadar is an independent project. It is not affiliated with GitHub, npm, PyPI, deps.dev, OSV, or any project it reports on. The verdict does not depend on who asks, who pays, or what a project would like to be said. There are no ads on RepoRadar.
Disputing or rechecking a report
Every report lists the rules that fired, each with links to the GitHub, package or advisory pages behind it. If you think something is wrong, check those links first. Then:
- Recheck. A recheck recomputes the report from current data. Rechecks are rate-limited for each repo. If the repo has changed, the verdict may change with it.
- Report a problem. Open an issue at https://github.com/TheChrisCross/reporadar-feedback/issues. Give the repo name and the rule you think is wrong, with a link to the evidence.
Please report errors in the data as well as in the rules. A rule that is correct but gives a surprising answer for an unusual repo is useful feedback too.
Contact
The public issue tracker is the way to reach us. Issues are visible to everyone, so do not post private information there. The privacy page says what we collect.