Discofork
Repository brief

LizardByte/Sunshine

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis
cached 2026-03-30T16:02:51.467Z
1mo ago

LizardByte/Sunshine

Sunshine is a self-hosted game stream host for Moonlight. It is an active, widely forked project with 35,659 stars and 1,799 forks, and it had commits pushed on 2026-03-30. The repo includes CMake, Docker, Python, Node/Vite, docs, tests, packaging, and third-party code, suggesting a cross-platform, multi-component codebase with installer/container and documentation support.

GitHub
Loading tags...
Stars35,659
Forks1,799
Default branchmaster
Last pushed2026-03-30T15:04:42Z
Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs
Selected

Choose this fork if HDR, virtual display, and custom input/encoder workflows matter more than upstream conservatism. Avoid it if you want the safest, most supportable Sunshine build with minimal divergence.

Choose this fork if you want a Windows-centered Sunshine variant with extra integration and display-management features. Stay with upstream if you value minimal drift, faster access to the latest fixes, and lower maintenance risk.

Choose this fork only if you need its custom behavior and are willing to own maintenance. For most adopters, upstream Sunshine is the safer choice because this fork is stale, heavily diverged, and likely behind on fixes and operational improvements.

Choose this fork only if its access-control, pairing, or packaging changes are the point. If you want the most stable path to upstream fixes and community support, upstream Sunshine is the safer default; this fork is a significant divergence with real maintenance and update risk.

Choose this fork only if you need its custom behavior and are prepared to own integration risk. For most adopters, upstream Sunshine is the safer choice because it is active and this fork is materially stale and highly divergent.

Prefer this fork only if you specifically want its client-control and capture/build changes and are prepared to live with a much older codebase. For most adopters, upstream looks safer because it is far more current and actively maintained.

Prefer this fork if you need the specific stream/runtime changes and are comfortable owning a large diff. Prefer upstream if you want the broadest feature completeness, docs, and lower maintenance risk.

Prefer upstream unless you specifically need this older snapshot. Adopt this fork only if you want a near-vanilla baseline and are prepared to catch up the 185 missing upstream commits yourself.

Choose this fork only if you specifically want a maintained-at-the-time snapshot with local packaging/UI tweaks and are prepared to own backporting; otherwise upstream is the safer default because this fork is stale and materially behind.

Choose this fork if GameAway-specific behavior and the added bitrate, access-control, and input/encoder changes matter more than staying close to upstream. Choose upstream if you want fresher maintenance, lower merge risk, and broader confidence in platform support.

LizardByte/Sunshine · Discofork