coplaydev/unity-mcp vs dotnet-architecture/eshoponcontainers
coplaydev/unity-mcp shows stronger signals overall
As of June 2026, unity-mcp shows healthier maintenance signals than eshoponcontainers. unity-mcp rates Healthy overall while eshoponcontainers rates Concerns. unity-mcp last saw a commit 1 month ago with 16+ active contributors, while eshoponcontainers last saw a commit 2 years ago with 12+ 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.
coplaydev/unity-mcp →
Healthy across the board
Permissive license, no critical CVEs, actively maintained — safe to depend on.
Has a license, tests, and CI — clean foundation to fork and modify.
Documented and popular — useful reference codebase to read through.
No critical CVEs, sane security posture — runnable as-is.
- ✓Last commit 5d ago
- ✓16 active contributors
- ✓Distributed ownership (top contributor 24% of recent commits)
- ✓MIT licensed
- ✓CI configured
- ✓Tests present
Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests
dotnet-architecture/eshoponcontainers →
Stale and unlicensed — last commit 2y ago
no license — legally unclear; last commit was 2y ago…
no license — can't legally use code; no tests detected…
Documented and popular — useful reference codebase to read through.
no license — can't legally use code; last commit was 2y ago…
- ⚠Stale — last commit 2y ago
- ⚠Concentrated ownership — top contributor handles 66% of recent commits
- ⚠No license — legally unclear to depend on
- ⚠No CI workflows detected
- ⚠No test directory detected
- ✓12 active contributors
What would improve this?
- →Use as dependency Concerns → Mixed if: publish a permissive license (MIT, Apache-2.0, etc.)
- →Fork & modify Concerns → Mixed if: add a LICENSE file
- →Deploy as-is Concerns → Mixed if: add a LICENSE file
Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests
Signal-by-signal breakdown
| unity-mcp | eshoponcontainers | |
|---|---|---|
| Stars | 9,415 | 24,383 |
| Last commit | 1mo ago | 2y ago |
| License | MIT | — |
| Open issues | 35 | 71 |
| Has tests | ✓ | — |
| Has CI | ✓ | — |
| Test coverage | 5% | — |
| Dependency CVEs | No CVEs | No CVEs |
| Architecture grade | — | — |
| Cycles | — | — |
| Bottom-line | Healthy signals | Concerns signals |
Want the full analysis? coplaydev/unity-mcp · dotnet-architecture/eshoponcontainers
Ask AI about coplaydev/unity-mcp vs dotnet-architecture/eshoponcontainers
Open the chat with a comparison question pre-filled.