Graphify-Labs/graphify
graphify
Turn any codebase, with its docs, SQL schemas, configs, and PDFs, into a queryable knowledge graph. A /graphify skill for Claude Code, Cursor, Codex, and Gemini CLI: local deterministic AST parsing, every edge explained, no vector store.
GitHub metrics
- Stars
- 126K
- +2.4K this week
- Forks
- 12K
- 30-day growth
- —
- Open issues
- 678
| Day | GitHub stars |
|---|---|
| 2026-10-04 | 123556 |
| 2026-10-10 | 125131 |
| 2026-10-13 | 125977 |
What it does
Graphify turns a software project and related material into a queryable knowledge graph. It parses code locally with tree-sitter, connects structures such as calls, imports and inheritance, and writes the result to graph.json. It can also produce an interactive graph.html viewer and a GRAPH_REPORT.md report. Queries can search the graph, explain a concept or trace a path between concepts.
Code analysis does not require an LLM or API key. Graphify distinguishes relationships extracted directly from source from relationships resolved by Graphify. It does not use embeddings or a vector store for its graph. Documents, PDFs and images can join the same graph, but their semantic processing uses an AI assistant or configured model backend rather than the code-only parser. The project also supplies a skill that can be registered with supported coding assistants including Claude Code, Cursor, Codex and Gemini CLI.
Why it matters
Graphify is aimed at codebase questions that depend on relationships across files rather than text matches alone. Its graph records calls, imports, inheritance and other links, and each relationship carries provenance indicating whether it came directly from source or was inferred. Unlike vector-search approaches, Graphify stores traversable graph data and provides query, path and explain operations against it.
Main features
- Parses code locally with tree-sitter ASTs.
- Builds cross-file call, import and inheritance relationships.
- Tags graph relationships as extracted or inferred.
- Supports query, path and explain operations.
- Exports `graph.json`, `graph.html` and `GRAPH_REPORT.md`.
- Can include docs, PDFs, images, video and audio.
- Integrates with more than 20 coding-assistant platforms.
Who it's for
- Developers exploring unfamiliar or large codebases.
- Teams that want code relationships available to AI coding assistants.
- Developers who want local, LLM-free structural analysis of source code.
- Projects that need code and supporting documents represented in one graph.
Strengths
- Code-only extraction runs locally without an LLM or API key.
- Relationship provenance separates directly extracted links from inferred ones.
- Queries operate on a graph rather than an embeddings index.
- A generated HTML file provides an interactive graph viewer.
Limitations
- Docs, PDFs and images require semantic processing through an assistant or configured backend.
- Several file formats and capabilities require optional package extras.
- After a git pull or merge, the README tells users to run `graphify update .`.
- OpenClaw and Aider use sequential extraction rather than parallel agent extraction.
Getting started
Python 3.10 or newer is required. The README recommends installing the CLI in an isolated environment with uv.
uv tool install graphifyy
Requirements: Python 3.10+; semantic extraction of docs or media needs an assistant model or configured model backend, while code-only extraction can run without an API key.
Always follow the official instructions in the README on GitHub. This overview is our summary, not a copy.
Sources
- Graphify-Labs/graphifyRepositoryPrimarygithub.com
- Graphify · the code knowledge graph for AI coding assistantsOfficial sitePrimarygraphify.com
- github.com/Graphify-Labs/graphify/blob/v8/pyproject.tomlRepositoryPrimary