Skip to main content
ArcSight

← HomepageAll repository proofValidation recordState of TS Architecture 2026

Repository proof

What ArcSight found in React Router

Real arc impact on React Router (packages/react-router) — blast radius, break paths, and evidence. Same question as the homepage: what breaks if I change this?

Project: React Router (packages/react-router) · Score: 72.9/100 (Moderate technical debt) · 69 modules · 289 edges

arc impact lib/router/history
Install ArcSight →Why trust ArcSight →

Run the same analysis on your repository in under 3 minutes.

Proof summary

Four questions every public repository page must answer — see validation record.

Modules to inspect

One row per module. Fan-in is direct dependents. Blast radius is downstream modules reachable from that file.

Fan-in, direct dependents
  • lib/router/utils35 dependents
  • lib/router/router24 dependents
  • lib/router/history20 dependents
  • lib/dom/ssr/routeModules17 dependents
  • lib/dom/ssr/entry16 dependents
  • lib/dom/ssr/routes11 dependents
  • lib/types/utils7 dependents
Blast radius, downstream modules
  • lib/router/history45 modules
  • lib/router/utils44 modules
  • lib/router/router43 modules
  • lib/dom/ssr/routeModules43 modules
  • lib/dom/ssr/entry43 modules
  • lib/dom/ssr/routes43 modules
ModuleFan-inBlastRisk
lib/router/history2045MEDIUM
lib/router/utils3544HIGH
lib/router/router2443MEDIUM
lib/dom/ssr/routeModules1743MEDIUM
lib/dom/ssr/entry1643CRITICAL
lib/dom/ssr/routes1143CRITICAL
lib/types/utils7MEDIUM

What ArcSight found

lib/router/history: fan-in 20, blast radius 45, MEDIUM. 69 modules and 289 dependency edges traced.

Why it matters

In React Router (packages/react-router), Change-risk signal at lib/router/history (fan-in 20) — merge impact can travel beyond the diff you see. Blast radius on lib/router/history reaches 45 downstream modules. ArcSight answers “what breaks if I change this?” before you ship; high fan-in is a change-risk signal, not a verdict on design quality.

What we'd inspect first

  • lib/router/history
  • lib/router/utils
  • lib/router/router

What evidence supports it

  • Local CLI analysis — repository source stays on your machine
  • Structural coverage: 69 modules, 289 edges in this snapshot
  • Reproducible fields match homepage live demo and frozen proof output

Architectural Risk Map

Where risk accumulates by control surface — drill down Surface → Substrate → Mechanism → Evidence.

See control surfaces →

Dependency evidence

Architecture visualization

Diagrams are generated from ArcSight analysis data. Dependency graph and risk map show key modules; subsystem view shows high-level structure.

Dependency graph
Dependency graph for this codebase
Subsystem architecture
Subsystem architecture for this codebase
Risk map
Risk map for this codebase

Architecture score & metrics

Score: 72.9/100 · Stability: 17/100 · Status: moderate_risk · Confidence: 100%

  • Dependency cycles: 49
  • Layer violations: 2
  • Duplicate authorities: 22

Architectural gravity centers

  • lib/router/history— concentrates too many responsibilities
  • lib/router/history— shared utility hub
  • lib/router/utils— concentrates too many responsibilities
  • lib/router/utils— shared utility hub
  • lib/router/utils— crosses a layer boundary

CLI workflow

Impact, then scan, fix, finish, and watch.

  • arc impact <file>See what a change breaks
  • arc scanFind issues
  • arc fixApply fixes
  • arc finishResolve remaining
  • arc watchKeep clean

More commands (explain, guard…) →

React Router (packages/react-router) architecture metrics
Score
72.9
Modules
69
Edges
289

Metrics

MetricValue
Architecture score72.9/100
Modules69
Edges289
Dependency cycles49

FAQ

What did ArcSight find in React Router (packages/react-router)?
lib/router/history: fan-in 20, blast radius 45, MEDIUM. 69 modules and 289 dependency edges traced.
Why does the React Router (packages/react-router) structure matter?
In React Router (packages/react-router), Change-risk signal at lib/router/history (fan-in 20) — merge impact can travel beyond the diff you see. Blast radius on lib/router/history reaches 45 downstream modules. ArcSight answers “what breaks if I change this?” before you ship; high fan-in is a change-risk signal, not a verdict on design quality.
Which file should I inspect first in React Router (packages/react-router)?
Start with lib/router/history. Run arc impact on that file before the change merges.

Key takeaways

  • •Structural scan reports dependency cycles — inspect impact paths before refactors that cross module boundaries.
  • •High fan-in modules are change-risk zones; run arc explain <path> before refactoring.
  • •Run the full workflow (analyze, hotspots, explain, impact, snapshot, drift) in your repo for deterministic architecture insights.

Run ArcSight on your repo

Install locally, then run arc impact on the file you plan to change — before merge.

npm install -g arcsight
arc impact <path>
Install ArcSight →

Embed this report

Use this iframe to show the architecture badge on your site.

<iframe src="https://arcsight.ai/embed/react-router/" width="320" height="180" frameborder="0"></iframe>

Evidence-backed analysis snapshot. Validation record · Install · Homepage demo