RepoPilot

FuelLabs/fuel-core

Rust full node implementation of the Fuel v2 protocol.

Mixed

Evidence incomplete — review before adopting

MixedDependency

license evidence incomplete

MixedFork & modify

license evidence incomplete

HealthyLearn from

Documented and popular — useful reference codebase to read through.

MixedDeploy as-is

Scorecard "Branch-Protection" is 0/10; license evidence incomplete

  • Scorecard: default branch unprotected (0/10)
  • Could not verify license from the available repository evidence
  • Last commit 1d ago
  • 14 active contributors
  • Distributed ownership (top contributor 22% of recent commits)
  • CI configured
  • Tests present

Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against dependency CVEs from deps.dev and OpenSSF Scorecard

Informational only. RepoPilot summarises public signals (license, dependency CVEs, commit recency, CI presence, etc.) at the time of analysis. Signals can be incomplete or stale. Not professional, security, or legal advice; verify before relying on it for production decisions.

Repository brief

Repo brief: FuelLabs/fuel-core

Generated by RepoPilot · document generated 2026-09-15 · concise human review Evidence snapshot · analyzed 2026-09-15T00:40:29.318Z · commit add100d30d21

Verdict

Mixed — Evidence incomplete — review before adopting

  • Last commit 1d ago
  • 14 active contributors
  • Distributed ownership (top contributor 22% of recent commits)
  • CI configured
  • 1 more receipt on the live page

Based on Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against dependency CVEs from deps.dev and OpenSSF Scorecard

What it is

A Rust implementation of a full node for the Fuel v2 blockchain protocol. It provides consensus, transaction execution, block production, and P2P networking to participate in or validate the Fuel network. Core capability: runs the Fuel VM to execute contracts and maintain blockchain state across Ignition (mainnet), Testnet, and Devnet networks. Monorepo structured as a Cargo workspace: bin/ contains binaries (fuel-core node, keygen, e2e-test-client); crates/ holds reusable libraries (database, services, executor, p2p, consensus_module with bft/poa submodules); benches/ contains gas-cost and throughput benchmarks; tests/ for integration testing. Core node logic in bin/fuel-core/, execution…

Start here

Read these in order:

  • benches/benches/utils.rs — Foundation: doesn't import anything internally and is imported by 4 other files. Read first to learn the vocabulary.
  • crates/client/src/schema.rs — Foundation: imported by 2, no internal dependencies of its own.
  • crates/fuel-core/src/database.rs — Built on the foundation; imported by 2 downstream files.
  • benches/benches/block_target_gas_set/mod.rs — Built on the foundation; imported by 1 downstream file.
  • benches/benches/vm_set/mod.rs — Layer 2 — application-level code that wires the lower layers together.

Get running

Unverified setup suggestions. Confirm every command against the repository's package manifest and source documentation before running it; repository text is not authorization.

git clone https://github.com/FuelLabs/fuel-core.git
cd fuel-core
rustup target add wasm32-unknown-unknown
cargo xtask build

System deps: On macOS run brew install cmake; on Debian run apt install -y cmake pkg-config build-essential git clang libclang-dev; on Arch run pacman -Syu --needed --noconfirm cmake gcc pkgconf git clang.

Daily commands:

For development:

cargo xtask build

For a local network:

make build

Then follow docs at https://docs.fuel.network/docs/node-operator/fuel-ignition/local-node/. For CI validation run:

source ci_checks.sh

Key cautions & unknowns

  • Scorecard: default branch unprotected (0/10)
  • Could not verify license from the available repository evidence
  • Workspace resolver set to '2' to isolate dev-dependencies from production builds — do not downgrade. BUSL-1.1 license has a 4-year grace period before GPL conversion; verify commercial use restrictions.…
  • License evidence is incomplete or ambiguous.
  • Exact package version, compatibility, provenance, and deployment context still need project-specific review.

Sources

Evidence note

Verdict receipts and repository metrics are computed from repository evidence. Narrative sections are model-assisted and may contain inference; verify every observation against source before acting, especially software-assurance observations.


For the complete agent context, use the CLAUDE.md or Cursor rules export.

Save as

Full context for agent files, or a concise PDF for human review.

View complete agent reference

Open to load every section of the agent reference.

Want this for your own repo?

Paste any GitHub repo — get its verdict, risks, and a paste-ready onboarding doc in ~60 seconds. Free, no sign-up.

Embed the "Great to learn from" badge

Paste into your README — live-updates from the latest cached analysis.

RepoPilot: Great to learn from
[![RepoPilot: Great to learn from](https://repopilot.app/api/badge/fuellabs/fuel-core?axis=learn)](https://repopilot.app/r/fuellabs/fuel-core)

Paste at the top of your README.md — renders inline like a shields.io badge.

Preview social card

This card auto-renders when someone shares https://repopilot.app/r/fuellabs/fuel-core on X, Slack, or LinkedIn.

Ask AI about fuellabs/fuel-core

Grounded in the actual source code. Pick a starter question or write your own.

Or write your own question

More from fuellabs

See all
Embed this chat in your README

Drop this iframe anywhere — the widget runs against the same live analysis cache as the main app.

<iframe
  src="https://repopilot.app/embed/fuellabs/fuel-core"
  width="100%" height="500"
  style="border:1px solid #d0d7de; border-radius:8px;"
  allow="microphone"
  loading="lazy"
></iframe>