Understand a GitHub repository in 30 seconds.
RepoSignal analyzes engineering health using public repository evidence.
Examples: facebook/react, vercel/next.js, prisma/prisma
What RepoSignal measures
Seven categories, each scored independently and each fully explainable. Weights are shown because they are a judgment call, not a fact.
- Repository Activityweight 15
- Commit cadence, last push, and how recently and regularly it releases.
- Pull Request Healthweight 15
- How long pull requests stay open, and how quickly they merge.
- Issue Healthweight 15
- Backlog age, stale issues, and whether issues close as fast as they arrive.
- CI Healthweight 15
- Whether automated checks exist on the default branch, and whether they pass.
- Documentationweight 15
- README, LICENSE, CONTRIBUTING, templates, and a documentation directory.
- Repository Hygieneweight 15
- Lockfiles, dependency automation, CODEOWNERS, tags, and metadata.
- Security Hygieneweight 10
- A security policy, dependency automation, and scanning declared in CI.
How the scores work
Every number can be traced back to the public GitHub data it came from. Each category shows the metrics examined, their raw values, the weights applied, the thresholds used, and links to the evidence.
Missing data is not treated as bad news. When something cannot be observed — GitHub has not computed commit statistics, or branch protection needs permissions RepoSignal does not have — it is reported as unknown and excluded from the score, with its weight redistributed across what could be measured. It is never counted as zero.
RepoSignal reports what it can observe. It does not read your code, does not scan for vulnerabilities, and does not use a language model to produce or adjust any score.