gograph

Coding · tested 2026-08-25 · re-test due 2026-11-23 · by the Hlido desk, not the vendor

In short: Compiler-aware repository context for Go coding agents — a local structural graph with optional type-checked enrichment, and a genuinely unusual commitment to publishing its own benchmark ground truth.

5 PASS · 0 FAIL of 5 public-surface claims

Quick answer

gograph scores 80/100 (STEADY) on Hlido’s independent, hands-on test (reviewed 2026-08-25). STEADY (80) because gograph is compiler-aware (type-checked CHA/SSA), agent-native via CLI and MCP, and — rare and creditable — publishes its own benchmark ground truth, exact commands and raw output against a ripgrep ba

gograph builds a local structural graph of a Go repository — callers, interface implementations, change-impact, architecture enforcement — usable from the CLI or as an MCP server, with no embeddings and no hosted code index. Its differentiator is being compiler-aware: an optional type-checked CHA/SSA enrichment (`build . --precise`) means it can resolve interface implementations and call paths with more precision than a pure-AST tool, while still tolerating incomplete packages for a fast first pass. The commands are practical and honest about their limits — `stats` verifies build health and analysis precision, `flow --no-tests` surfaces potential production source-to-sink paths — and the docs point you at running `--precise` before a major refactor. What genuinely sets this apart from the crowded code-context field is the Evidence view: gograph publishes a separate page preserving 'the precise benchmark, declared ground truth, exact commands, and complete raw output', and compares its results against plain ripgrep on three structural examples. Publishing your ground truth and raw output, and inviting a comparison against a baseline, is the opposite of the vendor-benchmark hand-wave — it is exactly the honesty a rating service rewards. The ceiling on the score is scope: it is Go-only by design, which is the right call for precision but narrows the audience, and it is a young single-language tool without a broad adoption signal on the surface. Within its lane, though, this is one of the more rigorously presented code-intelligence tools in the batch.

Why STEADY

STEADY (80) because gograph is compiler-aware (type-checked CHA/SSA), agent-native via CLI and MCP, and — rare and creditable — publishes its own benchmark ground truth, exact commands and raw output against a ripgrep baseline rather than asserting results. It is held at 80 rather than higher because it is deliberately Go-only, which narrows its audience, and it is a young tool without a broad public adoption signal.

Public-surface checklist

What we saw

4 screenshots captured by the Hlido engine during the reviewed run (run-ac1b02cba78739c5-gograph-identuum-ai). Our own captures — not vendor marketing material.

gograph — run screenshot 1 (home.png)
home.png
gograph — run screenshot 2 (page_.png)
page_.png
gograph — run screenshot 3 (page_demo_.png)
page_demo_.png
gograph — run screenshot 4 (page_docs_getting-started_.png)
page_docs_getting-started_.png

What it does well

What it fails at

Best for

  • Go teams whose coding agent needs precise, compiler-aware structural context
  • Engineers planning a major Go refactor who want call-graph and change-impact analysis
  • Developers who value a tool that publishes its benchmark ground truth and raw output

Not recommended for

  • Polyglot codebases or any project not primarily in Go
  • Teams needing a commercially supported product with SLAs
  • Workflows that need embeddings-based semantic search rather than structural analysis

Pricing & access

Derived from Hlido-held evidence only (engine checklist + editorial text); quotes are verbatim from the scorecard; not vendor-supplied; re-derived daily. Verify current prices on the vendor's pricing page. Last verified 2026-08-25.

Compared to

Agent relevance

CLI MCP Behavioral-testable

Agentic-Commerce Readiness 67/100 · INTEGRABLE

Independent readiness for agent delegation & transaction. How it’s scored · check live

Usable as an MCP server or CLI. A Go coding agent calls gograph to build the structural graph and then query callers, interface implementations, hotspots, change-impact and source-to-sink flows — with type-checked precision when the repo compiles. No embeddings or hosted index; everything runs locally. The published command set maps cleanly to agent tool calls.

Agent-friendly score: 8/10

Evidence

scorecard.json · transparency passport · registry · methodology

More: compare agents · best of · developer tools · incident registry

Verdict by Hlido Editor, our automated editorial system · Method: public-surface-tier-1+editorial-narrative-v2 · Methodology version 2026.05 · Next review due 2026-11-23

How this page was produced. The scores, claim verdicts and evidence come from automated hands-on testing of the product’s public surface. The written analysis is drafted by an AI system, and pages publish without a person reviewing each one. Hlido publishes this record and answers for it — tell us if anything here is wrong and we will correct it.

Embed this trust badge

Hlido trust score

Live, always-current independent score — free to embed on your site or README. No vendor pays for placement.

Markdown

[![Hlido trust score](https://hlido.eu/badge/ozgurcd-gograph.svg)](https://hlido.eu/check/?agent=ozgurcd-gograph)

HTML

<a href="https://hlido.eu/check/?agent=ozgurcd-gograph"><img src="https://hlido.eu/badge/ozgurcd-gograph.svg" alt="Hlido trust score"></a>