Discofork
Repository brief

shadowsocks/shadowsocks-windows

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-30T13:27:32.610Z
3mo ago

shadowsocks/shadowsocks-windows

Shadowsocks for Windows is a mature C# Windows client for Shadowsocks with very high adoption: 59,278 stars and 16,282 forks. It is not archived, targets .NET Framework 4.8+, and appears actively maintained with a recent commit on 2025-01-01. Forks are most likely interesting if you want to customize proxy behavior, PAC rules, server selection, or plugin support in a Windows desktop client.

GitHub
Loading tags...
Stars59,278
Forks16,282
Default branchv4
Last pushed2025-01-01T08:09:55Z
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

Prefer upstream unless you specifically need this old snapshot. The fork shows no added capability and is far behind, so it is a poor choice for general adopters.

Choose this fork only if you specifically want its older portable/UI-oriented changes and are comfortable trading away years of upstream maintenance; otherwise upstream is the safer default.

Prefer upstream unless you specifically need the crawler-based free-server workflow. This fork is narrowly useful, materially outdated, and a poor choice for anyone who wants a maintained Windows Shadowsocks client.

Choose this fork only if its portable-mode and UI/log workflow changes are exactly what you need. For most adopters, upstream is the safer choice because this fork is extremely stale and materially behind on maintenance and newer capabilities.

Prefer upstream unless you specifically need this old snapshot. This fork shows no added capabilities and is far behind upstream, so it is a poor choice for users who want current fixes or features.

Choose this fork only if you need a stale, unchanged historical copy. For normal use, upstream is clearly the better choice because it is actively maintained and far ahead in fixes and features.

Choose this fork if you want the project as a modernized, modular proxy platform. Stick with upstream if you want the most stable, familiar Windows desktop experience and fewer compatibility surprises.

Choose upstream unless you have a specific reason to preserve this old fork state. This fork looks like a stale snapshot with no clearly demonstrated added value.

Do not adopt this fork for normal use. The evidence points to an abandoned, unchanged snapshot that is far behind upstream; prefer current upstream unless you specifically need the 2018 state.

Choose this fork only if embedded kcptun is the feature you need. For general Shadowsocks-on-Windows use, upstream is the safer choice because this fork is old and far behind.