FuelLabs/sway

Choose this fork only if its custom `forc`/compiler features are the point and you are prepared to own a large, stale divergence. For most adopters, upstream is the safer choice because it is much newer and better maintained.

Choose this fork only if you explicitly want an older, heavily modified Sway codebase and are prepared to maintain it yourself. If you want an actively maintained toolchain for real development, upstream is the better fit.

Prefer this fork only if you need its custom debugging/compiler changes and are prepared to own a long-lived downstream maintenance burden. For most adopters, current upstream is the better choice because this fork is materially stale and appears to remove standard-library capabilities.

Choose this fork only if you need its specific downstream behavior and are prepared to maintain a large divergence. If you want current Sway features, fixes, and release compatibility, upstream is the safer choice.

Choose this fork only if you need its custom debugger-oriented branch or historical 2024 behavior. For normal Sway development, upstream is the better choice because it is far more current and likely has better tooling, fixes, and ecosystem compatibility.

Prefer this fork only if you need its specific local changes and are willing to own a large maintenance backlog. For most users, upstream is the better choice because this fork is materially behind and heavily diverged.