facebook/pyre-check vs google/pytype
google/pytype shows stronger signals overall
As of September 2026, pytype shows healthier maintenance signals than pyre-check. pytype rates Healthy overall while pyre-check rates Mixed. pyre-check last saw a commit 2 months ago with 12+ active contributors, while pytype last saw a commit 6 months ago with 9+ active contributors. Both use the MIT license. Neither has known critical or high-severity CVEs in its dependency tree.
Informational only. RepoPilot summarises public signals at the time of analysis. Not professional, security, or legal advice.
facebook/pyre-check
OpenSSF Scorecard says this is unmaintained
dependency CVE scan unavailable
No blocking repository signals were found — inspect the evidence before forking.
Documented and popular — useful reference codebase to read through.
Scorecard "Token-Permissions" is 0/10; dependency CVE scan unavailable
- ⚠Concentrated ownership — top contributor handles 77% of recent commits
- ⚠Scorecard: marked unmaintained (0/10)
- ✓Last commit 2mo ago
- ✓12 active contributors
- ✓MIT licensed
- ✓CI configured
- ✓Tests present
Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against OpenSSF Scorecard
google/pytype
Healthy across all four use cases
No blocking maintenance, license, or known-CVE signals were found; still verify the package version and fit.
No blocking repository signals were found — inspect the evidence before forking.
Documented and popular — useful reference codebase to read through.
No blocking repository-level signals were found; deployment review is still required.
- ⚠Slowing — last commit 6mo ago
- ⚠Scorecard: marked unmaintained (0/10)
- ✓Last commit 6mo ago
- ✓9 active contributors
- ✓Distributed ownership (top contributor 49% of recent commits)
- ✓MIT licensed
- ✓CI configured
- ✓Tests present
Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against dependency CVEs from deps.dev and OpenSSF Scorecard
Signal-by-signal breakdown
| pyre-check | pytype | |
|---|---|---|
| Stars | 7,171 | 5,031 |
| Last commit | 2mo ago | 6mo ago |
| License | MIT | MIT |
| Open issues | 167 | 5 |
| Has tests | ✓ | ✓ |
| Has CI | ✓ | ✓ |
| Test coverage | 100% | 77% |
| Dependency CVEs | No CVEs | No CVEs |
| Architecture grade | — | — |
| Cycles | — | — |
| Bottom-line | Mixed signals | Healthy signals |
Want the full analysis? facebook/pyre-check · google/pytype
Ask AI about facebook/pyre-check vs google/pytype
Open the chat with a comparison question pre-filled.