9001/copyparty

Choose this fork if your priority is a simpler, customized copyparty deployment and you do not need upstream’s full protocol/UI surface. Stick with upstream if you want the broadest feature set, active maintenance, and lower compatibility risk.

Adopt this only if you explicitly want a frozen older copyparty base; otherwise upstream looks like the better choice because this fork shows no added capabilities and is materially behind.

Choose this fork only if you want an upstream-equivalent snapshot. If you want newer features or fixes, upstream is the better choice.

Choose upstream unless you specifically need this exact fork state; this fork adds no visible capabilities and is behind recent upstream work.

Choose this fork only if you want a clean, upstream-aligned starting point. If you want recent features, fixes, or active downstream maintenance, upstream itself looks like the better choice.

Prefer upstream for most use cases. This fork shows no added functionality and is materially behind, so it only makes sense if you want this exact snapshot or to build your own downstream on top of it.

Choose this fork only if you specifically want an unmodified upstream snapshot. For anyone looking for new capabilities, active maintenance, or reduced operational risk, upstream is the better default.

Prefer upstream unless you specifically need this exact older snapshot; this fork adds no visible value and is behind current development.

Prefer upstream unless you specifically need this frozen February 2026 snapshot; this fork does not show added capabilities and is materially behind current upstream.