andeya/pholcus vs avelino/awesome-go
Both showing Healthy signals — pick on fit, not health
As of June 2026, pholcus and awesome-go both show healthy maintenance signals. pholcus last saw a commit 3 months ago with 17+ active contributors, while awesome-go was committed to today with 76+ active contributors. pholcus is Apache-2.0-licensed while awesome-go 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.
andeya/pholcus →
Healthy across the board
Permissive license, no critical CVEs, actively maintained — safe to depend on.
Has a license, tests, and CI — clean foundation to fork and modify.
Documented and popular — useful reference codebase to read through.
No critical CVEs, sane security posture — runnable as-is.
- ⚠Concentrated ownership — top contributor handles 74% of recent commits
- ⚠Scorecard: default branch unprotected (0/10)
- ✓Last commit 2mo ago
- ✓17 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 OpenSSF Scorecard
avelino/awesome-go →
Healthy across the board
Permissive license, no critical CVEs, actively maintained — safe to depend on.
Has a license, tests, and CI — clean foundation to fork and modify.
Documented and popular — useful reference codebase to read through.
Scorecard "Branch-Protection" is 0/10; Scorecard "Token-Permissions" is 0/10
- ⚠Scorecard: dangerous CI workflow (0/10)
- ⚠Scorecard: default branch unprotected (0/10)
- ✓Last commit today
- ✓76+ active contributors
- ✓Distributed ownership (top contributor 10% of recent commits)
- ✓MIT licensed
- ✓CI configured
- ✓Tests present
What would improve this?
- →Deploy as-is Mixed → 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
| pholcus | awesome-go | |
|---|---|---|
| Stars | 7,590 | 176,527 |
| Last commit | 3mo ago | today |
| License | Apache-2.0 | MIT |
| Open issues | 0 | 184 |
| Has tests | ✓ | ✓ |
| Has CI | ✓ | ✓ |
| Test coverage | 3% | 10% |
| Dependency CVEs | No CVEs | No CVEs |
| Architecture grade | — | — |
| Cycles | — | — |
| Bottom-line | Healthy signals | Healthy signals |
Want the full analysis? andeya/pholcus · avelino/awesome-go
Ask AI about andeya/pholcus vs avelino/awesome-go
Open the chat with a comparison question pre-filled.