ewenwan/mvision vs valvesoftware/proton
valvesoftware/proton shows stronger signals overall
As of June 2026, proton shows stronger maintenance signals than mvision. proton rates Mixed overall while mvision rates Concerns. mvision last saw a commit 1 year ago with 1+ active contributor, while proton last saw a commit 1 month 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.
ewenwan/mvision →
Looks unmaintained — solo project with stale commits
no license — legally unclear; last commit was 2y ago…
no license — can't legally use code; no CI workflows 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
- ⚠Solo or near-solo (1 contributor active in recent commits)
- ⚠No license — legally unclear to depend on
- ⚠No CI workflows detected
- ✓Tests present
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
valvesoftware/proton →
Mixed signals — read the receipts
non-standard license (Other); no tests detected…
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.
- ⚠Non-standard license (Other) — review terms
- ⚠No CI workflows detected
- ⚠No test directory detected
- ✓Last commit today
- ✓12 active contributors
- ✓Distributed ownership (top contributor 36% of recent commits)
- ✓Other licensed
What would improve this?
- →Use as dependency Concerns → Mixed if: clarify license terms
Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests
Signal-by-signal breakdown
| mvision | proton | |
|---|---|---|
| Stars | 8,625 | 31,365 |
| Last commit | 1y ago | 1mo ago |
| License | — | Other |
| Open issues | 19 | 5,073 |
| Has tests | ✓ | — |
| Has CI | — | — |
| Test coverage | 5% | 0% |
| Dependency CVEs | No CVEs | No CVEs |
| Architecture grade | — | — |
| Cycles | — | — |
| Bottom-line | Concerns signals | Mixed signals |
Want the full analysis? ewenwan/mvision · valvesoftware/proton
Ask AI about ewenwan/mvision vs valvesoftware/proton
Open the chat with a comparison question pre-filled.