avelino/awesome-go vs yeasy/blockchain_guide
avelino/awesome-go shows stronger signals overall
As of June 2026, awesome-go shows healthier maintenance signals than blockchain_guide. awesome-go rates Healthy overall while blockchain_guide rates Mixed. awesome-go was committed to today with 76+ active contributors, while blockchain_guide last saw a commit 1 month ago with 3+ active contributors. 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
yeasy/blockchain_guide →
Missing license — unclear to depend on
no license — legally unclear; top contributor handles 90% of recent commits…
no license — can't legally use code; no tests detected
Documented and popular — useful reference codebase to read through.
no license — can't legally use code
- ⚠Small team — 3 contributors active in recent commits
- ⚠Single-maintainer risk — top contributor 90% of recent commits
- ⚠No license — legally unclear to depend on
- ⚠No test directory detected
- ✓Last commit 5d ago
- ✓3 active contributors
- ✓CI configured
What would improve this?
- →Use as dependency Concerns → Mixed if: publish a permissive license (MIT, Apache-2.0, etc.)
- →Fork & modify Concerns → Mixed if: add a LICENSE file
- →Deploy as-is Concerns → Mixed if: add a LICENSE file
Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests
Signal-by-signal breakdown
| awesome-go | blockchain_guide | |
|---|---|---|
| Stars | 176,527 | 7,067 |
| Last commit | today | 1mo ago |
| License | MIT | — |
| Open issues | 184 | 1 |
| 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 · yeasy/blockchain_guide
Ask AI about avelino/awesome-go vs yeasy/blockchain_guide
Open the chat with a comparison question pre-filled.