avelino/awesome-go vs mrs4s/go-cqhttp
Both showing Healthy signals — pick on fit, not health
As of September 2026, awesome-go and go-cqhttp both show healthy maintenance signals. awesome-go was committed to 2 weeks ago with 56+ active contributors, while go-cqhttp last saw a commit 2 months ago with 30+ active contributors. awesome-go is MIT-licensed while go-cqhttp is AGPL-3.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
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: dangerous CI workflow (0/10)
- ⚠Scorecard: default branch unprotected (0/10)
- ✓Last commit today
- ✓56+ active contributors
- ✓Distributed ownership (top contributor 10% 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
mrs4s/go-cqhttp
Strong maintenance signals
copyleft license (AGPL-3.0) — review compatibility
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
- ⚠AGPL-3.0 is copyleft — check downstream compatibility
- ⚠Scorecard: default branch unprotected (0/10)
- ⚠1 moderate-severity advisory on direct dependencies
- ✓Last commit 6w ago
- ✓30+ active contributors
- ✓Distributed ownership (top contributor 32% of recent commits)
- ✓AGPL-3.0 licensed
- ✓CI configured
- ✓Tests present
What would improve this?
- •Use as dependency Concerns to Mixed if: relicense under MIT/Apache-2.0 (rare for established libs)
- •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
| awesome-go | go-cqhttp | |
|---|---|---|
| Stars | 182,930 | 10,636 |
| Last commit | 14d ago | 2mo ago |
| License | MIT | AGPL-3.0 |
| Open issues | 223 | 314 |
| Has tests | ✓ | ✓ |
| Has CI | ✓ | ✓ |
| Test coverage | 100% | 6% |
| Dependency CVEs | 0 critical · 0 high · 1 moderate · 0 low | 0 critical · 0 high · 1 moderate · 0 low |
| Architecture grade | A | A |
| Cycles | 0 | 0 |
| Bottom-line | Healthy signals | Healthy signals |
Want the full analysis? avelino/awesome-go · mrs4s/go-cqhttp
Ask AI about avelino/awesome-go vs mrs4s/go-cqhttp
Open the chat with a comparison question pre-filled.