MobiusSync/syncthing
active
significant_divergence
Selected Choose this fork if you want a materially different Syncthing experience, especially around the next-generation GUI and customized behavior. Choose upstream if you want the safest path, fastest access to fixes, and the least integration risk.
isyncthing/syncthing
stale
significant_divergence
Prefer upstream unless you explicitly need this fork's older baseline or custom modifications and are prepared to maintain a large divergence yourself.
calmh/syncthing
stale
significant_divergence
Do not adopt this fork as a general-purpose Syncthing base. It looks stale, heavily stripped, and far behind upstream; only choose it if you specifically want a placeholder or cleanup branch.
canton7/syncthing
stale
significant_divergence
Prefer upstream unless you already rely on this fork’s legacy behavior. This fork adds a few concrete UI and runtime fixes, but its age and drift make it a poor default choice for new adopters.
tvvocold/syncthing
stale
significant_divergence
Choose this fork only if you need its specific old tweaks and are prepared to own a long-dead codebase. For most adopters, upstream Syncthing is the clearly better choice because this fork is far behind and likely missing years of fixes and improvements.
AudriusButkevicius/syncthing
stale
significant_divergence
Prefer this fork only if you specifically need its older GUI/API behavior. For most adopters, upstream is the better choice because this fork is stale, materially behind, and likely missing important safety and maintenance fixes.
Lennix/syncthing
stale
significant_divergence
Prefer this fork only if encrypted filenames are the main goal and you are comfortable maintaining a very old, heavily diverged codebase. For most adopters, upstream is the safer choice because this fork is stale and missing years of fixes and maintenance.
chenxiaolong/syncthing
stale
significant_divergence
Choose this fork only if you want a heavily customized BasicSync-oriented base and are prepared to own major upstream drift. If you want current Syncthing behavior with minimal maintenance risk, upstream is the safer choice.
emlun/syncthing
stale
significant_divergence
Prefer upstream if you want the safest, most current Syncthing. Prefer this fork only if the next-gen GUI direction is the main reason you are adopting and you are willing to absorb the maintenance and rebasing cost.
fragtion/syncthing
slowing
significant_divergence
Choose this fork if you want the custom UI and internal experimentation it seems to be pursuing. Choose upstream if you want current fixes, lower risk, and a more stable maintenance path.