go-kratos/kratos vs googleapis/mcp-toolbox
Both showing Healthy signals — pick on fit, not health
As of September 2026, kratos and mcp-toolbox both show healthy maintenance signals. kratos was committed to 4 weeks ago with 35+ active contributors, while mcp-toolbox was committed to 3 weeks ago with 33+ active contributors. kratos is MIT-licensed while mcp-toolbox is Apache-2.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.
go-kratos/kratos
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)
- ⚠Scorecard: dangerous CI workflow (0/10)
- ✓Last commit 4w ago
- ✓35+ active contributors
- ✓Distributed ownership (top contributor 29% 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
googleapis/mcp-toolbox
Strong maintenance signals
dependency CVE scan unavailable
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; 1 cyclic import chain detected…
- ⚠Scorecard: default branch unprotected (0/10)
- ✓Last commit today
- ✓33+ active contributors
- ✓Distributed ownership (top contributor 16% of recent commits)
- ✓Apache-2.0 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 OpenSSF Scorecard
Signal-by-signal breakdown
| kratos | mcp-toolbox | |
|---|---|---|
| Stars | 25,928 | 16,262 |
| Last commit | 29d ago | 21d ago |
| License | MIT | Apache-2.0 |
| Open issues | 115 | 245 |
| Has tests | ✓ | ✓ |
| Has CI | ✓ | ✓ |
| Test coverage | 63% | 100% |
| Dependency CVEs | No CVEs | No CVEs |
| Architecture grade | — | A |
| Cycles | — | 1 |
| Bottom-line | Healthy signals | Healthy signals |
Want the full analysis? go-kratos/kratos · googleapis/mcp-toolbox
Ask AI about go-kratos/kratos vs googleapis/mcp-toolbox
Open the chat with a comparison question pre-filled.