FuelLabs/fuels-ts

Adopt this fork only if you specifically need its custom SDK behavior and are prepared to maintain a long-lived divergence. For most users, upstream is the safer choice because this fork is stale, materially behind, and likely incompatible with current Fuel ecosystem releases.

Choose this fork only if you need its specific 2024-era additions and are prepared to own maintenance. For most adopters, upstream is the safer choice because this fork is stale and substantially behind.

Prefer upstream unless you specifically need this older predicate/crypto refactor line. The fork appears useful as a historical snapshot or for niche experimentation, but it is too stale and divergent to be a safe default for production adoption.

Prefer upstream unless you specifically need this fork's older 2023-era behavior or custom patches. This fork is materially stale, so adopting it means inheriting a large maintenance burden and likely missing current Fuel SDK compatibility.

Adopt only if you specifically need an old snapshot. For any serious SDK, CLI, or Fuel-network work, upstream is the better choice because this fork adds nothing and is materially behind current maintenance.

Choose this fork only if you need its older customized Fuel SDK behavior and are prepared to own the maintenance burden. For most adopters, upstream is the safer choice because this fork is stale and materially diverged.

Prefer this fork only if its older custom CLI/typegen/local-node behavior is specifically what you need and you are prepared to maintain a large divergence yourself. For most adopters, upstream is the better default because this fork is stale and materially behind.

Choose the upstream project if you want current Fuel compatibility and lower maintenance risk. Choose this fork only if you specifically need its customized SDK internals and are prepared to absorb a large divergence from upstream.