avelino/awesome-go vs go-gorm/gorm
Both showing Healthy signals — pick on fit, not health
As of September 2026, awesome-go and gorm both show healthy maintenance signals. awesome-go was committed to 2 weeks ago with 56+ active contributors, while gorm last saw a commit 2 months ago with 58+ active contributors. Both use the MIT license. 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
go-gorm/gorm
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.
- ⚠Scorecard: marked unmaintained (2/10)
- ✓Last commit 2mo ago
- ✓58+ active contributors
- ✓Distributed ownership (top contributor 26% of recent commits)
- ✓MIT 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
Signal-by-signal breakdown
| awesome-go | gorm | |
|---|---|---|
| Stars | 182,930 | 39,937 |
| Last commit | 14d ago | 2mo ago |
| License | MIT | MIT |
| Open issues | 223 | 524 |
| Has tests | ✓ | ✓ |
| Has CI | ✓ | ✓ |
| Test coverage | 100% | 100% |
| Dependency CVEs | 0 critical · 0 high · 1 moderate · 0 low | No CVEs |
| Architecture grade | A | — |
| Cycles | 0 | — |
| Bottom-line | Healthy signals | Healthy signals |
Want the full analysis? avelino/awesome-go · go-gorm/gorm
Ask AI about avelino/awesome-go vs go-gorm/gorm
Open the chat with a comparison question pre-filled.