FuelLabs/fuels-rs

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.