/jump to repo

Repos Recent Bookmarks Watched Notes Tags Discover Compare Stats GitHub

Repository brief

FuelLabs/sway

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-30T12:08:08.709Z

3mo ago

FuelLabs/sway

FuelLabs/sway is an active Rust-based smart contract language and toolchain for the Fuel blockchain. It is widely used and well-maintained, with 61,840 stars, 5,426 forks, and recent commits as of 2026-03-27. Forks are most interesting if you care about blockchain language/compiler work, developer tooling, or contract infrastructure.

Loading tags...

Stars61,840

Forks5,426

Default branchmaster

Last pushed2026-03-27T13:44:57Z

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

7 of 7 fork briefs

Maintenance:

Magnitude:

Sort:

Selected

Prefer this fork only if you intentionally need the older 0.60-era Sway behavior or its fork-specific test/ABI fixes. For new development or active maintenance, upstream is the better default because this fork is stale and materially behind.

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.

Fork comparison

Zikc2023/sway

38/100

stale

significant_divergence

Prefer this fork only if you intentionally need the older 0.60-era Sway behavior or its fork-specific test/ABI fixes. For new development or active maintenance, upstream is the better default because this fork is stale and materially behind.

Likely purpose

A pinned, older Sway fork for experimenting with a 0.60-era compiler/toolchain and local CI/test fixes rather than tracking upstream master.

Best for

Developers maintaining legacy Sway code against an older toolchain.; Researchers comparing compiler or language behavior across Sway releases.; Contributors who want to study or patch a 2024-era snapshot instead of current upstream.; Teams with an existing fork-specific workflow that already depends on these older changes.

Additional features

Added ABI encode/decode support for `String` and related storage handling improvements.
Added language/runtime conveniences like `Self::zero`, `self::is_zero()`, and `OrdEq` on `U128`.
Includes optimizer and compiler behavior tweaks such as contract-call argument unification, inline/fndedup pipeline changes, and fuelvm instruction bug fixes.
Improved local testing/CI workflows, including default-funding for test accounts and safer plugin-path warnings.
Expands API, schema, or SDK surface area for downstream integrations and generated clients.
Adds plugin, tool, or MCP-style extensibility beyond the upstream baseline.

Missing features

Lags far behind upstream master and appears anchored to an older `v0.60.0` line instead of the current `0.70.3` workspace.
Appears to drop or heavily rework standard-library helpers such as `codec.sw` and `debug.sw`, which may make some upstream examples or APIs unavailable.
Likely misses newer upstream compiler, optimizer, LSP, formatter, and plugin work shipped after mid-2024.
Upstream documentation and release-era workflows are newer than this fork's last push, so adopters would not get current bugfixes or language features.
It trails upstream by 200 commits, so some recent upstream features and fixes are likely not present yet.

Strengths

Useful if you need the older behavior that matches the fork's 2024-era state.
Contains concrete fixes that improve smart-contract authoring and test harness reliability.
May be easier to study if you want a smaller, older snapshot of Sway internals and language changes.

Risks

Very stale relative to upstream, so compatibility, security, and bugfix debt are likely high.
Large divergence makes upstream docs, examples, and tooling harder to apply directly.
Removed or reorganized standard-library files may break downstream code expecting current upstream APIs.

FuelLabs/sway · Discofork