go-gorm/gorm vs uptrace/bun
Both showing Healthy signals — pick on fit, not health
As of September 2026, gorm and bun both show healthy maintenance signals. gorm last saw a commit 2 months ago with 58+ active contributors, while bun was committed to 3 weeks ago with 25+ active contributors. gorm is MIT-licensed while bun is BSD-2-Clause-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.
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
uptrace/bun
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: default branch unprotected (0/10)
- ✓Last commit 4w ago
- ✓25+ active contributors
- ✓Distributed ownership (top contributor 27% of recent commits)
- ✓BSD-2-Clause 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
Signal-by-signal breakdown
| gorm | bun | |
|---|---|---|
| Stars | 39,937 | 4,973 |
| Last commit | 2mo ago | 26d ago |
| License | MIT | BSD-2-Clause |
| Open issues | 524 | 40 |
| Has tests | ✓ | ✓ |
| Has CI | ✓ | ✓ |
| Test coverage | 100% | 28% |
| Dependency CVEs | No CVEs | 0 critical · 0 high · 5 moderate · 0 low |
| Architecture grade | — | — |
| Cycles | — | — |
| Bottom-line | Healthy signals | Healthy signals |
Want the full analysis? go-gorm/gorm · uptrace/bun
Ask AI about go-gorm/gorm vs uptrace/bun
Open the chat with a comparison question pre-filled.