← 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/utilsRun the same analysis on your repository in under 3 minutes.
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.
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 responsibilitieslib/router/history— shared utility hublib/router/utils— concentrates too many responsibilitieslib/router/utils— shared utility hublib/router/utils— crosses a layer boundary
Try it in the terminal
Simulated arc analyze output from the dataset. No analysis runs in the browser.
Simulated from dataset. No analysis is run in the browser.
Similar architectures
Repositories with the same language and category, ordered by similar complexity and size.
CLI workflow
Impact, then scan, fix, finish, and watch.
arc impact <file>See what a change breaksarc scanFind issuesarc fixApply fixesarc finishResolve remainingarc watchKeep clean
- Score
- 72.9
- Modules
- 69
- Edges
- 289
Metrics
| Metric | Value |
|---|---|
| Architecture score | 72.9/100 |
| Modules | 69 |
| Edges | 289 |
| Dependency cycles | 49 |
FAQ
- What did ArcSight find in React Router (packages/react-router)?
- React Router (packages/react-router) has 69 modules and an architecture score of 72.9/100.
- Why does the React Router (packages/react-router) structure matter?
- The React Router (packages/react-router) score is 72.9/100 across 69 modules and 289 edges.
- Which file should I inspect first in React Router (packages/react-router)?
- Start with lib/router/utils. 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.
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>Explore
Evidence-backed analysis snapshot. Validation record · Install · Homepage demo