myshell-ai/openvoice vs public-apis/public-apis
public-apis/public-apis shows stronger signals overall
As of June 2026, public-apis shows healthier maintenance signals than openvoice. public-apis rates Healthy overall while openvoice rates Mixed. openvoice last saw a commit 1 year ago with 12+ active contributors, while public-apis was committed to 3 days ago with 23+ active contributors. Both use the MIT license. 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.
myshell-ai/openvoice →
Stale — last commit 1y ago
last commit was 1y ago; no tests detected…
Has a license, tests, and CI — clean foundation to fork and modify.
Documented and popular — useful reference codebase to read through.
last commit was 1y ago; no CI workflows detected
- ⚠Stale — last commit 1y ago
- ⚠Concentrated ownership — top contributor handles 63% of recent commits
- ⚠No CI workflows detected
- ⚠No test directory detected
- ✓12 active contributors
- ✓MIT licensed
What would improve this?
- →Use as dependency Mixed → Healthy if: 1 commit in the last 365 days; add a test suite
- →Deploy as-is Mixed → Healthy if: 1 commit in the last 180 days
Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests
public-apis/public-apis →
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.
- ⚠Concentrated ownership — top contributor handles 75% of recent commits
- ⚠Scorecard: default branch unprotected (0/10)
- ✓Last commit 1d ago
- ✓23+ active contributors
- ✓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
Signal-by-signal breakdown
| openvoice | public-apis | |
|---|---|---|
| Stars | 36,483 | 444,088 |
| Last commit | 1y ago | 3d ago |
| License | MIT | MIT |
| Open issues | 301 | 1,458 |
| Has tests | — | ✓ |
| Has CI | — | ✓ |
| Test coverage | 0% | 100% |
| Dependency CVEs | No CVEs | No CVEs |
| Architecture grade | — | — |
| Cycles | — | — |
| Bottom-line | Mixed signals | Healthy signals |
Want the full analysis? myshell-ai/openvoice · public-apis/public-apis
Ask AI about myshell-ai/openvoice vs public-apis/public-apis
Open the chat with a comparison question pre-filled.