shadowsocks/shadowsocks-windows

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.