Solutions
Map every connection in your code.
Your codebase has thousands of dependencies that nobody documented. Axiom Refract computes the full dependency graph — with confidence scoring, transitive closures, and cluster detection — from the actual code, not from memory.
Why dependency maps matter.
Your mental model is wrong.
Every team has a picture of their architecture in their heads. In most cases, it's aspirational — how the system was supposed to work, not how it actually works. The dependency graph doesn't lie. It's computed from AST analysis of every file, every import, every call site.
Refactoring without a map is gambling.
You want to extract a service, split a module, or deprecate a package. Without a dependency graph, you're guessing at the blast radius. With one, you know exactly which files, which zones, and which teams are affected before you write a single line of code.
Onboarding shouldn't take months.
New engineers spend weeks building a mental model of how the codebase fits together. A dependency graph gives them that model on day one — interactive, searchable, and accurate.
What Axiom's dependency graph includes.
Confidence-Scored Edges
Not all imports are equal. Axiom Refract assigns confidence levels to every dependency edge — hard imports (explicit, static) vs soft imports (dynamic, inferred). You see not just what connects to what, but how certain that connection is.
Transitive Closures
File A imports File B, which imports File C. Most tools stop at direct imports. Axiom Refract computes the full transitive closure — so when you change File C, you know that File A is affected even though it never mentions File C directly.
Cluster Detection
Files that form natural groups get identified automatically. These clusters become zones — logical boundaries that emerge from the code itself, not from folder conventions or someone's mental model of the architecture.
Centrality Scoring
Every node in the graph gets a composite centrality score combining PageRank, betweenness centrality, and degree metrics. The files that matter most to your system's stability float to the top — whether your team recognizes them or not.
Blast Radius Calculation
Select any file and see its forward dependents — every file that breaks if this one changes. BFS traversal up to configurable depth. The answer to “what happens if I touch this?” before you touch it.
See it. Query it. Act on it.
Interactive Viewer
The dependency graph renders in Axiom Refract's web-based viewer. Zoom, pan, filter by zone, click any node to see its dependents and dependencies. No desktop app required — it runs in your browser.
MCP Integration for AI Agents
Your AI coding agents can query the dependency graph directly via MCP. Ask “what depends on this file?” or “what's the blast radius of changing this module?” and get structured answers from the actual graph — not from the LLM's training data.
JSON + DOCX + Diagrams
Every analysis exports the dependency graph in machine-readable JSON, human-readable DOCX, and visual C4 diagrams. One scan, every consumer served.
Map the dependencies nobody documented.
Point Axiom Refract at your repository. Get a complete dependency graph with confidence scoring, centrality metrics, and blast radius calculations — in minutes, not sprints.