google/skia vs lizardbyte/sunshine
Both showing Healthy signals — pick on fit, not health
As of September 2026, skia and sunshine both show healthy maintenance signals. skia was committed to 3 weeks ago with 16+ active contributors, while sunshine was committed to 1 week ago with 18+ active contributors. skia is BSD-3-Clause-licensed while sunshine is GPL-3.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.
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
lizardbyte/sunshine
Strong maintenance signals
copyleft license (GPL-3.0) — review compatibility
No blocking repository signals were found — inspect the evidence before forking.
Documented and popular — useful reference codebase to read through.
No blocking repository-level signals were found; deployment review is still required.
- ⚠GPL-3.0 is copyleft — check downstream compatibility
- ⚠Scorecard: default branch unprotected (0/10)
- ✓Last commit today
- ✓18 active contributors
- ✓Distributed ownership (top contributor 31% of recent commits)
- ✓GPL-3.0 licensed
- ✓CI configured
- ✓Tests present
What would improve this?
- •Use as dependency Concerns to Mixed if: relicense under MIT/Apache-2.0 (rare for established libs)
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
| skia | sunshine | |
|---|---|---|
| Stars | 10,895 | 40,814 |
| Last commit | 22d ago | 10d ago |
| License | BSD-3-Clause | GPL-3.0 |
| Open issues | 50 | 143 |
| Has tests | ✓ | ✓ |
| Has CI | No | ✓ |
| Test coverage | 59% | 28% |
| Dependency CVEs | No CVEs | No CVEs |
| Architecture grade | C | A |
| Cycles | 0 | 0 |
| Bottom-line | Healthy signals | Healthy signals |
Want the full analysis? google/skia · lizardbyte/sunshine
Ask AI about google/skia vs lizardbyte/sunshine
Open the chat with a comparison question pre-filled.