Skip to main content
A graph edge connects a source node to a target node. Its relation explains the connection, such as calls, imports, inherits, or references.

Confidence labels

An inferred edge can be derived without a model. Static name and import resolution can infer cross-file relationships, while a semantic backend can infer connections between documents and code. How Graphify finds code dependencies explains each step.

Direction matters

A calls B differs from B calls A. The current path command and MCP shortest_path tool respect stored direction by default. Use --undirected in the CLI or undirected: true in MCP to explore connectivity regardless of direction.
These are example names. Replace them with nodes from your project.

A path is evidence, not a runtime guarantee

Source-level calls may be conditional or dynamically resolved. A path shows the relationships in the analyzed graph; it does not prove a request will execute that path or that a change is safe. Use formal verification in Graphify to compare supported changed functions. Graph traversal itself is not a formal proof.

Next steps

Try it in Graphify

We build and host the graph for you. The Free plan (up to 3 repositories) needs no card. Pro and Teams start with a 14-day trial, card required.

Graph files and outputs

What a build writes and how to reuse it.

Ask better graph questions

Use query, path, and explain.