Discofork
Repository brief

9001/copyparty

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-30T11:44:30.852Z
3mo ago

9001/copyparty

copyparty is an actively maintained, popular Python-based portable file server. It focuses on resumable uploads/downloads and bundles multiple access protocols and file-serving features into one package. For fork interest, it looks especially relevant if you want a mature, feature-rich file transfer/server codebase with broad protocol support and a large upstream user base.

GitHub
Loading tags...
Stars43,887
Forks1,792
Default branchhovudstraum
Last pushed2026-03-30T08:43:10Z
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 this fork only if its UI and deployment changes match your exact needs and you can accept losing SFTP, translations, and upstream parity. For most adopters who want the full copyparty feature set and lower maintenance risk, upstream is the safer choice.

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.

9001/copyparty · Discofork