Inspiration
A small PR that touches a shared helper can break services several call hops away. The diff looks fine; the blast radius is not visible from the change alone. I wanted that answer before merge, without an LLM and without an API key.
What it does
Cognee GitGraph is a Cognee community connector that loads a git repository into Cognee's graph: commits, file changes, Python symbols and call references, and CI failures from JUnit XML. From that graph it computes the blast radius of a branch or commit: which functions call the code you changed, how many hops away, which top-level services they live in, and which CI failures belong to those services.
The default path is plain graph traversal over extracted rows, so it makes zero LLM calls. Optional --remember loads the same rows into Cognee's local embedded stores (fastembed + GLiNER on first run).
bun run demo builds a sample monorepo, changes verify_token, and prints at-risk services, co-changed files, and CI failures. There is also a 3D force-graph page of the blast radius and a narrated demo video.
How we built it
- Python package with a Cognee connector at
packages/connector/gitgraph(proposed for cognee-community) - Symbol and reference extraction for Python, JUnit CI parsing, blast-radius walk
- CLI (
blast, demo, real-repo against karpathy/nanochat), optional Cognee load - Community PRs: connector #560 and blast radius / CLI / 3D #561
- Proposal issue: topoteretes/cognee#6329
- Write-up: What breaks if I change verify_token?
Challenges
Keeping the happy path keyless and deterministic while still integrating with Cognee's graph for the optional remember path. Splitting the community contribution into a connector PR and a blast-radius PR so reviewers can merge the smaller piece first. Making the demo and 3D view show the same blast report the CLI prints.
Try it
bun run setup
bun run demo
Source: https://github.com/chrisbuildsonline/cognee-gitgraph

