Graphtia documentation · feature
Explorer overview
Move between a project’s code graph and the source that gives it meaning.
Keep the question and the source together
Explorer provides a project tree, a graph of indexed relationships, source viewing and an inspector. These surfaces answer different questions. The tree locates an item; the graph explains nearby structure; the source shows the implementation; the inspector carries identity and evidence.
A first investigation
Open an indexed project and search for a recognizable module, such as checkout-service.ts.
Select the result and open graph + code. Check the source path before drawing a conclusion from a similar name.
Inspect the relationships around the module. Use dependencies to examine what it needs, and dependents to investigate consumers.
Check the indexed revision and any view notices. Read the source behind the relationship that matters to your question.
What the graph can tell you
The engine implements files, symbols, callers, callees, dependencies, dependents, references, paths, neighborhoods, impact candidates, related tests and findings. Results carry bounds and revision context. Availability and precision can differ by language and query.