MapnosticsDOCS
← Back to Main Site
DocsIntelligence ModulesImpact Simulator

Impact Simulator

Ask any "what if" question about your codebase and get a full dependency blast radius in seconds — before you write a single line of code. Built for safe refactors and zero-surprise deployments.

How it works

Mapnostics builds a complete import/export dependency graph and keeps it updated daily. When you submit a question, the simulator traces every downstream dependency of the target — direct imports, re-exports through barrel files, dynamic requires — and scores each affected file by risk level.

  • High Risk — directly depends on the changed code path, breaks without it.
  • Medium Risk — indirect dependency; may behave differently after the change.
  • Low Risk — loosely related, worth a manual spot-check.

Live demo

Watch the full simulation: query typing → dependency graph traversal → affected files with risk levels surfacing one by one. The window height stays fixed throughout.

mapnostics.com/repo/mapnostics-app/impact-simulator
Impact Simulator
Ask what breaks before you change anything
● LIVE
Ask a question about your codebase…
src/App.tsxHIGH RISK
ProtectedRoute and all admin routes are no longer secured.
src/middleware/auth.tsHIGH RISK
Core middleware removed — all downstream guards break.
src/components/admin/InvoiceView.tsxHIGH RISK
Invoice data exposed without authentication checks.
src/components/admin/Dashboard.tsxMEDIUM RISK
Admin dashboard accessible without login.
src/hooks/useSession.tsMEDIUM RISK
Session validation depends on middleware context.

Reading the results

Risk levels

Risk reflects coupling, not importance. A HIGH file will almost certainly break. A MEDIUM file may behave unexpectedly. Use this to scope your test plan before merging.

NOTE
The simulator traces static imports only. Dynamic require(variable) calls are listed separately as potential unknowns.

Example queries

  • "What breaks if I remove the auth middleware?"
  • "What depends on UserContext?"
  • "Which files import from src/utils/legacy-format.ts?"
  • "What would break if I delete the legacy payment module?"
TIP
Combine with Dead Code Detection — zero dependents in the simulator AND a dead code flag = safe to delete with very high confidence.