fatedier/frp vs valyala/fasthttp
Both showing Healthy signals — pick on fit, not health
As of September 2026, frp and fasthttp both show healthy maintenance signals. frp was committed to 2 weeks ago with 11+ active contributors, while fasthttp last saw a commit 1 month ago with 18+ active contributors. frp is Apache-2.0-licensed while fasthttp is MIT-licensed. 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.
fatedier/frp
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.
- ⚠Single-maintainer risk — top contributor 88% of recent commits
- ✓Last commit 1d ago
- ✓11 active contributors
- ✓Apache-2.0 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
valyala/fasthttp
Strong maintenance signals
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.
Scorecard "Branch-Protection" is 0/10; Scorecard "Token-Permissions" is 0/10
- ⚠Scorecard: default branch unprotected (0/10)
- ⚠1 moderate-severity advisory on direct dependencies
- ✓Last commit 5d ago
- ✓18 active contributors
- ✓Distributed ownership (top contributor 29% of recent commits)
- ✓MIT licensed
- ✓CI configured
- ✓Tests present
What would improve this?
- •Deploy as-is Mixed to Healthy if: bring "Branch-Protection" to ≥3/10 (see scorecard report)
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
| frp | fasthttp | |
|---|---|---|
| Stars | 109,091 | 23,439 |
| Last commit | 18d ago | 1mo ago |
| License | Apache-2.0 | MIT |
| Open issues | 49 | 90 |
| Has tests | ✓ | ✓ |
| Has CI | ✓ | ✓ |
| Test coverage | 59% | 86% |
| Dependency CVEs | No CVEs | 0 critical · 0 high · 1 moderate · 0 low |
| Architecture grade | — | — |
| Cycles | — | — |
| Bottom-line | Healthy signals | Healthy signals |
Want the full analysis? fatedier/frp · valyala/fasthttp
Ask AI about fatedier/frp vs valyala/fasthttp
Open the chat with a comparison question pre-filled.