Discofork
Repository brief

FuelLabs/fuels-ts

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-30T20:05:57.616Z
1mo ago

FuelLabs/fuels-ts

FuelLabs/fuels-ts is the official TypeScript SDK for the Fuel network. It is a large, active, non-archived repository with a very high fork count and star count, and it includes both SDK code and tooling for building, testing, type generation, deployment, and local node workflows. Forks are most interesting if you care about the Fuel ecosystem, TypeScript SDK development, or CLI/tooling around Sway/Fuel Core integration.

GitHub
Loading tags...
Stars43,282
Forks1,368
Default branchmaster
Last pushed2026-03-27T18:21:29Z
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 a frozen snapshot. This fork adds no visible functionality, is materially behind current upstream, and is best treated as an archival or private baseline rather than an actively maintained SDK fork.

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.