lizardbyte/sunshine vs prusa3d/prusaslicer
lizardbyte/sunshine shows stronger signals overall
As of June 2026, sunshine shows healthier maintenance signals than prusaslicer. sunshine rates Healthy overall while prusaslicer rates Mixed. sunshine last saw a commit 1 month ago with 18+ active contributors, while prusaslicer last saw a commit 2 months ago with 10+ active contributors. sunshine is GPL-3.0-licensed while prusaslicer is AGPL-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.
lizardbyte/sunshine →
Healthy across the board
copyleft license (GPL-3.0) — review compatibility
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.
- ⚠GPL-3.0 is copyleft — check downstream compatibility
- ⚠Scorecard: default branch unprotected (0/10)
- ✓Last commit today
- ✓18 active contributors
- ✓Distributed ownership (top contributor 27% of recent commits)
- ✓GPL-3.0 licensed
- ✓CI configured
- ✓Tests present
What would improve this?
- →Use as dependency Concerns → 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 OpenSSF Scorecard
prusa3d/prusaslicer →
Mixed signals — read the receipts
copyleft license (AGPL-3.0) — review compatibility; no tests detected
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 51% of recent commits
- ⚠AGPL-3.0 is copyleft — check downstream compatibility
- ⚠No test directory detected
- ✓Last commit 2w ago
- ✓10 active contributors
- ✓AGPL-3.0 licensed
- ✓CI configured
What would improve this?
- →Use as dependency Concerns → 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
Signal-by-signal breakdown
| sunshine | prusaslicer | |
|---|---|---|
| Stars | 36,974 | 8,999 |
| Last commit | 1mo ago | 2mo ago |
| License | GPL-3.0 | AGPL-3.0 |
| Open issues | 106 | 5,584 |
| Has tests | ✓ | — |
| Has CI | ✓ | ✓ |
| Test coverage | 47% | 0% |
| Dependency CVEs | No CVEs | No CVEs |
| Architecture grade | — | — |
| Cycles | — | — |
| Bottom-line | Healthy signals | Mixed signals |
Want the full analysis? lizardbyte/sunshine · prusa3d/prusaslicer
Ask AI about lizardbyte/sunshine vs prusa3d/prusaslicer
Open the chat with a comparison question pre-filled.