karpathy/llm-council vs public-apis/public-apis
public-apis/public-apis shows stronger signals overall
As of June 2026, public-apis shows healthier maintenance signals than llm-council. public-apis rates Healthy overall while llm-council rates Mixed. llm-council last saw a commit 7 months ago with 1+ active contributor, while public-apis was committed to 3 days ago with 23+ 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.
karpathy/llm-council →
Slowing — last commit 6mo ago
no license — legally unclear; single-maintainer (no co-maintainers visible)…
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; no CI workflows detected
- ⚠Slowing — last commit 6mo ago
- ⚠Solo or near-solo (1 contributor active in recent commits)
- ⚠No license — legally unclear to depend on
- ⚠No CI workflows detected
- ⚠No test directory detected
- ✓Last commit 6mo ago
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
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
| llm-council | public-apis | |
|---|---|---|
| Stars | 18,509 | 444,088 |
| Last commit | 7mo ago | 3d ago |
| License | — | MIT |
| Open issues | 122 | 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? karpathy/llm-council · public-apis/public-apis
Ask AI about karpathy/llm-council vs public-apis/public-apis
Open the chat with a comparison question pre-filled.