Solutions

Find the files your system can't survive without.

A single point of failure in code isn't a server that goes down — it's a file that, if it breaks, cascades failure across your entire system. Axiom Refract finds these files, quantifies their blast radius, and ranks them by risk.

What a SPOF looks like in code.

Infrastructure teams have monitored single points of failure for decades — the one database server, the one load balancer, the one DNS provider. But the same concept applies inside your codebase.

A code-level SPOF is a file with extreme structural importance: dozens of other files depend on it, either directly or through transitive chains. If that file has a bug, a breaking change, or an outage-causing regression, the failure doesn't stay contained. It propagates.

The question isn't whether your codebase has SPOFs. It does. The question is whether you know which files they are and how far the damage reaches.

Why traditional tools miss SPOFs.

Linters see syntax, not structure

Traditional static analysis tools check code quality at the file level. They find unused variables and code smells. They have no concept of system-wide dependency cascades.

Manual reviews can't scale

A senior engineer might intuit that one module is “important.” But can they quantify that it has 47 transitive dependents across 3 architectural zones? At 50,000+ lines, intuition breaks down.

Dependency trees aren't dependency graphs

Package managers show you what your code imports. They don't show you what happens when something fails. A SPOF isn't about what a file uses — it's about what uses it.

How Axiom quantifies every SPOF.

Each SPOF is scored across four dimensions. No opinions — just graph math.

Centrality Score

A composite of PageRank, betweenness centrality, and in-degree. Files with critical or high centrality are the structural backbone of your system.

Blast Radius

The number of files that break — directly or transitively — if this file fails. Computed via BFS traversal of the dependency graph, up to configurable depth.

Zone Impact

Which architectural zones are affected. A SPOF that impacts one zone is a local risk. A SPOF that spans three zones is a systemic one.

Dependent Count

Direct dependents (files that import this file) and transitive dependents (files that depend on those files). The full cascade, quantified.

SPOFs don't hide in the viewer.

In Axiom Refract's interactive dependency viewer, SPOF nodes are rendered with a pulsing red glow — visually distinct from every other file in the graph. You don't search for them. They announce themselves.

Click a SPOF node and the viewer highlights its entire blast radius: every file that would be affected, colored by dependency depth. First-order dependents in amber. Transitive dependents fading outward. The cascade is visible at a glance.

This isn't a table of metrics buried in a report. It's a spatial representation of risk that makes the problem impossible to ignore in architecture reviews and sprint planning.