Repo brief: graphprotocol/graph-node

Generated by RepoPilot · document generated 2026-09-16 · concise human review Evidence snapshot · analyzed 2026-09-16T23:10:14.868Z · commit aefe17371c67

Verdict

Healthy — Strong maintenance signals

• Last commit 1d ago
• 6 active contributors
• Distributed ownership (top contributor 44% of recent commits)
• Apache-2.0 licensed
• 2 more receipts on the live page

Based on Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests

What it is

Graph Node is a Rust-based blockchain indexing engine that extracts, transforms, and serves blockchain data via GraphQL. It reads events and state from blockchains (Ethereum, NEAR, etc.) through Firehose providers or RPC, stores normalized data in PostgreSQL, and exposes it as queryable GraphQL APIs. It's the core infrastructure behind The Graph Protocol's decentralized indexing network. Monorepo with Cargo workspace. Core logic in core/ (indexing state machine), chain/ (Ethereum, NEAR adapters), store/postgres/ (PostgreSQL persistence layer), runtime/wasm/ (WASM execution for subgraph mappings), and server/ (HTTP, GraphQL, JSON-RPC endpoints). Shared types in graph/ crate. Firehose…

Start here

Open these first:

• Cargo.toml — Workspace root configuration defining all member crates, dependencies (alloy, tokio, etc.), and version…
• chain/ethereum/src/lib.rs — Entry point for Ethereum chain integration; defines core trait implementations and adapters that all blockchain indexing…
• core/src/amp_subgraph/manager.rs — Core subgraph lifecycle management; orchestrates deployment, execution, and state tracking for all indexed subgraphs.
• chain/ethereum/src/chain.rs — Ethereum-specific chain abstraction implementing block streaming, transaction handling, and chain event ingestion logic.
• chain/ethereum/src/ingestor.rs — Block ingestion pipeline that handles polling/streaming blocks and feeding them into the indexing engine—critical data…

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.

rustup install stable
git clone https://github.com/graphprotocol/graph-node.git
cd graph-node
psql -U postgres <<'EOF'
create user graph with password 'graph';
create database "graph-node" with owner=graph template=template0 encoding='UTF8' locale='C';
create extension pg_trgm;
create extension btree_gist;
create extension postgres_fdw;
grant usage on foreign data wrapper postgres_fdw to graph;
EOF
DATABASE_URL=postgres://graph:graph@localhost/graph-node \
  ETHEREUM_RPC_URL=http://localhost:8545 \
  IPFS_HOST=http://localhost:5001 \
  cargo run --release -p graph-node

Requires: PostgreSQL 12+, Protobuf compiler, IPFS daemon, Ethereum RPC (local or Infura/Alchemy), and Rust 1.80+.

Daily commands:

cargo build --release
cargo test --all --release

…shortened for this brief.

Key cautions & unknowns

• PostgreSQL version/extensions: Must use PostgreSQL 12+. Extensions pg_trgm, btree_gist, postgres_fdw are required and will cause silent failures if missing—check with \dx in psql. Reorg handling: Ethereum…
• Published-advisory coverage was unavailable for the captured dependencies.
• Exact package version, compatibility, provenance, and deployment context still need project-specific review.

Sources

• Repository source
• Open issues
• Recent pull requests

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.