go-kratos/kratos vs yaoapp/yao
go-kratos/kratos shows stronger signals overall
As of September 2026, kratos shows healthier maintenance signals than yao. kratos rates Healthy overall while yao rates Mixed. kratos was committed to 4 weeks ago with 35+ active contributors, while yao was committed to 1 week ago with 2+ 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.
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
yaoapp/yao
Single-maintainer risk — review before adopting
top contributor handles 99% of recent commits; license evidence incomplete…
license evidence incomplete
Documented and popular — useful reference codebase to read through.
Scorecard "Branch-Protection" is 0/10; license evidence incomplete…
- ⚠Small team — 2 contributors active in recent commits
- ⚠Single-maintainer risk — top contributor 99% of recent commits
- ⚠Scorecard: default branch unprotected (0/10)
- ✓Last commit 2d ago
- ✓2 active contributors
- ✓CI configured
- ✓Tests present
Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against OpenSSF Scorecard
Signal-by-signal breakdown
| kratos | yao | |
|---|---|---|
| Stars | 25,928 | 7,900 |
| Last commit | 29d ago | 11d ago |
| License | MIT | Unknown |
| Open issues | 115 | 7 |
| Has tests | ✓ | ✓ |
| Has CI | ✓ | ✓ |
| Test coverage | 63% | 68% |
| Dependency CVEs | No CVEs | No CVEs |
| Architecture grade | — | C |
| Cycles | — | 0 |
| Bottom-line | Healthy signals | Mixed signals |
Want the full analysis? go-kratos/kratos · yaoapp/yao
Ask AI about go-kratos/kratos vs yaoapp/yao
Open the chat with a comparison question pre-filled.