ggml-org/llama.cpp vs google/skia
Both showing Healthy signals — pick on fit, not health
As of September 2026, llama.cpp and skia both show healthy maintenance signals. llama.cpp was committed to today with 50+ active contributors, while skia was committed to 3 weeks ago with 16+ active contributors. llama.cpp is MIT-licensed while skia is BSD-3-Clause-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.
ggml-org/llama.cpp
Strong maintenance signals
No blocking maintenance, license, or known-CVE signals were found; still verify the package version and fit.
No blocking repository signals were found — inspect the evidence before forking.
Documented and popular — useful reference codebase to read through.
Scorecard "Branch-Protection" is 0/10; 1 cyclic import chain detected
- ⚠Scorecard: default branch unprotected (0/10)
- ⚠1 moderate-severity advisory on direct dependencies
- ✓Last commit today
- ✓50+ active contributors
- ✓Distributed ownership (top contributor 9% of recent commits)
- ✓MIT licensed
- ✓CI configured
- ✓Tests present
What would improve this?
- •Deploy as-is Mixed to 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 dependency CVEs from deps.dev and OpenSSF Scorecard
google/skia
Strong maintenance signals
no CI workflows detected; dependency CVE scan unavailable
No blocking repository signals were found — inspect the evidence before forking.
Documented and popular — useful reference codebase to read through.
Scorecard "Branch-Protection" is 0/10; no CI workflows detected…
- ⚠No CI workflows detected
- ⚠Scorecard: default branch unprotected (0/10)
- ✓Last commit today
- ✓16 active contributors
- ✓Distributed ownership (top contributor 35% of recent commits)
- ✓BSD-3-Clause licensed
- ✓Tests present
What would improve this?
- •Deploy as-is Mixed to 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
| llama.cpp | skia | |
|---|---|---|
| Stars | 128,131 | 10,895 |
| Last commit | today | 23d ago |
| License | MIT | BSD-3-Clause |
| Open issues | 2,469 | 50 |
| Has tests | ✓ | ✓ |
| Has CI | ✓ | No |
| Test coverage | 16% | 59% |
| Dependency CVEs | 0 critical · 0 high · 1 moderate · 0 low | No CVEs |
| Architecture grade | A | C |
| Cycles | 1 | 0 |
| Bottom-line | Healthy signals | Healthy signals |
Want the full analysis? ggml-org/llama.cpp · google/skia
Ask AI about ggml-org/llama.cpp vs google/skia
Open the chat with a comparison question pre-filled.