avelino/awesome-go vs lk-geimfari/awesomo
avelino/awesome-go shows stronger signals overall
As of June 2026, awesome-go shows healthier maintenance signals than awesomo. awesome-go rates Healthy overall while awesomo rates Mixed. awesome-go was committed to today with 76+ active contributors, while awesomo last saw a commit 2 years ago with 2+ active contributors. awesome-go is MIT-licensed while awesomo is CC0-1.0-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.
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
lk-geimfari/awesomo →
Stale — last commit 2y ago
last commit was 2y ago; no tests detected…
no tests detected; no CI workflows detected…
Documented and popular — useful reference codebase to read through.
last commit was 2y ago; no CI workflows detected
- ⚠Stale — last commit 2y ago
- ⚠Small team — 2 contributors active in recent commits
- ⚠Concentrated ownership — top contributor handles 50% of recent commits
- ⚠No CI workflows detected
- ⚠No test directory detected
- ✓2 active contributors
- ✓CC0-1.0 licensed
What would improve this?
- →Use as dependency Mixed → Healthy if: 1 commit in the last 365 days; add a test suite
- →Fork & modify Mixed → Healthy if: add a test suite
- →Deploy as-is Mixed → Healthy if: 1 commit in the last 180 days
Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests
Signal-by-signal breakdown
| awesome-go | awesomo | |
|---|---|---|
| Stars | 176,527 | 9,852 |
| Last commit | today | 2y ago |
| License | MIT | CC0-1.0 |
| Open issues | 184 | 6 |
| Has tests | ✓ | — |
| Has CI | ✓ | — |
| Test coverage | 10% | 0% |
| Dependency CVEs | No CVEs | No CVEs |
| Architecture grade | — | — |
| Cycles | — | — |
| Bottom-line | Healthy signals | Mixed signals |
Want the full analysis? avelino/awesome-go · lk-geimfari/awesomo
Ask AI about avelino/awesome-go vs lk-geimfari/awesomo
Open the chat with a comparison question pre-filled.