public-apis/public-apis vs zai-org/open-autoglm
public-apis/public-apis shows stronger signals overall
As of June 2026, public-apis shows healthier maintenance signals than open-autoglm. public-apis rates Healthy overall while open-autoglm rates Mixed. public-apis was committed to 3 days ago with 23+ active contributors, while open-autoglm last saw a commit 3 months ago with 13+ active contributors. public-apis is MIT-licensed while open-autoglm 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.
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
zai-org/open-autoglm →
Mixed signals — read the receipts
no tests detected; no CI workflows detected
Has a license, tests, and CI — clean foundation to fork and modify.
Documented and popular — useful reference codebase to read through.
Scorecard "Branch-Protection" is 0/10; no CI workflows detected
- ⚠No CI workflows detected
- ⚠No test directory detected
- ⚠Scorecard: default branch unprotected (0/10)
- ✓Last commit 2mo ago
- ✓13 active contributors
- ✓Distributed ownership (top contributor 39% of recent commits)
- ✓Apache-2.0 licensed
What would improve this?
- →Use as dependency Mixed → Healthy if: add a test suite
- →Deploy as-is Mixed → 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
| public-apis | open-autoglm | |
|---|---|---|
| Stars | 444,088 | 25,289 |
| Last commit | 3d ago | 3mo ago |
| License | MIT | Apache-2.0 |
| Open issues | 1,458 | 254 |
| Has tests | ✓ | — |
| Has CI | ✓ | — |
| Test coverage | 100% | 0% |
| Dependency CVEs | No CVEs | No CVEs |
| Architecture grade | — | — |
| Cycles | — | — |
| Bottom-line | Healthy signals | Mixed signals |
Want the full analysis? public-apis/public-apis · zai-org/open-autoglm
Ask AI about public-apis/public-apis vs zai-org/open-autoglm
Open the chat with a comparison question pre-filled.