Discofork
Repository brief

FuelLabs/fuels-rs

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-31T09:56:34.096Z
1mo ago

FuelLabs/fuels-rs

FuelLabs/fuels-rs is the Rust SDK for the Fuel network. It supports compiling, deploying, and testing Sway contracts, launching a local Fuel network, crafting and signing transactions, generating type-safe Rust bindings, running scripts, and providing a CLI for common operations. The repository is active, with 43,325 stars, 1,359 forks, and a recent push on 2026-03-12.

GitHub
Loading tags...
Stars43,325
Forks1,359
Default branchmaster
Last pushed2026-03-12T20:54:19Z
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

9 of 9 fork briefs
Selected

Prefer upstream unless you specifically need an early-2025 frozen snapshot. This fork offers no evident added capability and is mostly valuable only as a static reference or compatibility baseline.

Choose upstream unless you specifically need this older, customized SDK line. This fork looks best for low-level experimentation or legacy compatibility, not for most adopters wanting an actively maintained Fuel SDK.

Choose this fork only if you specifically want its experimental SDK changes and are prepared to maintain a long-lived divergence. For most adopters, upstream is the safer default because this fork is stale and appears to have shed parts of the upstream test and workflow surface.

Prefer upstream unless you specifically need this fork's legacy/custom behavior. This fork looks like a stale, highly diverged customization branch, not a current baseline for new Fuel development.

Prefer upstream unless you specifically need this exact older revision. This fork adds no visible capabilities and is significantly behind active upstream work, so it mainly suits archival or pinning use cases.

Choose this fork only if you need its specific older, heavily modified SDK behavior. For most users, upstream is the better default because it is far more current, actively maintained, and likely to have more complete features and documentation.

Choose this fork only if you want the upstream SDK almost exactly as-is and are fine being slightly behind. If you want active feature work, bugfixes, or long-term maintenance, upstream is the better default.

Prefer upstream unless you specifically need a frozen 2024 snapshot. This fork adds no visible value over upstream and is materially behind current SDK work.

Choose this only if you need the older 2024-era SDK snapshot; otherwise upstream is the better default because this fork adds no visible capabilities and is materially behind.