Skip to main content
ArcSight

← Homepage

Impact analysis example

What breaks when you change Nitro?

Real arc impact output on Nitro — same structure as the homepage demo. Know blast radius before you merge.

Project: Nitro · Score: 92.9/100 (Excellent architecture) · 224 modules · 283 edges

Engineering decision simulation

Validation procedure 01 · merge vs. hold before output

Before arc impact

You plan a change to a high fan-in module in Nitro. Would you merge without knowing blast radius?

Typical answer: hold — need dependency context.

After arc impact

Structured output below: score, hotspots, corridors, and high-risk modules — same field schema as the homepage proof.

Decision: confirm hold, narrow change, or inspect paths first.

Published as part of the validation record. Run locally: arc impact <file-you-are-changing>

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: 92.9/100 · Stability: 36/100 · Status: healthy · Confidence: 100%

  • Dependency cycles: 5
  • Duplicate authorities: 13

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
  • src/presets/_utils/preset32 dependents
  • src/runtime/virtual/_runtime_warn15 dependents
  • src/presets/_utils/fs8 dependents
  • src/utils/fs7 dependents
  • src/types/config6 dependents
  • src/types/nitro4 dependents
  • src/types/hooks3 dependents
  • src/types/fetch/fetch3 dependents
Blast radius, downstream modules
  • src/presets/_utils/preset50 modules
  • src/presets/_utils/fs28 modules
  • src/utils/fs28 modules
  • src/runtime/virtual/_runtime_warn15 modules
  • src/types/config7 modules
  • src/types/nitro7 modules
  • src/types/hooks7 modules
  • src/types/preset7 modules
ModuleFan-inBlastRisk
src/presets/_utils/preset3250HIGH
src/presets/_utils/fs828MEDIUM
src/utils/fs728LOW
src/runtime/virtual/_runtime_warn1515LOW
src/types/config67CRITICAL
src/types/nitro47CRITICAL
src/types/hooks37CRITICAL
src/types/preset27HIGH
src/types/fetch/fetch34HIGH
src/presets/vercel/runtime/isr3LOW

Architectural gravity centers

  • src/presets/_utils/preset— concentrates too many responsibilities
  • src/presets/_utils/preset— shared utility hub
  • src/runtime/virtual/_runtime_warn— shared utility hub

CLI workflow

Scan → Fix → Finish → Watch. Nothing else required.

  • arc scanFind issues
  • arc fixApply fixes
  • arc finishResolve remaining
  • arc watchKeep clean

More commands (explain, impact, guard…) →

Key takeaways

  • •Architecture score 92.9/100 indicates a healthy structure with room to reduce cycles and violations.
  • •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 the CLI and run analyze, then hotspots and explain for the same workflow.

npm install -g arcsight
arc analyze
Install ArcSight →

This case study is generated from ArcSight analysis data. View short analysis. View all analyses