Skip to main content
ArcSight

← Homepage

Impact analysis example

What breaks when you change Nuxt (packages/schema)?

Real arc impact output on Nuxt (packages/schema) — same structure as the homepage demo. Know blast radius before you merge.

Project: Nuxt (packages/schema) · Score: 94/100 (Excellent architecture) · 35 modules · 84 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 Nuxt (packages/schema). 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: 94/100 · Stability: 40/100 · Status: healthy · Confidence: 100%

  • Dependency cycles: 7
  • Layer violations: 2

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/utils/definition18 dependents
  • src/types/nuxt7 dependents
  • src/types/config5 dependents
  • src/types/module5 dependents
  • src/types/components4 dependents
  • src/types/debug4 dependents
  • src/types/head4 dependents
Blast radius, downstream modules
  • src/utils/definition26 modules
  • src/types/nuxt26 modules
  • src/types/config26 modules
  • src/types/module26 modules
  • src/types/components26 modules
  • src/types/debug26 modules
ModuleFan-inBlastRisk
src/utils/definition1826MEDIUM
src/types/nuxt726LOW
src/types/config526LOW
src/types/module526LOW
src/types/components426CRITICAL
src/types/debug426CRITICAL
src/types/head4LOW

Architectural gravity centers

  • src/utils/definition— concentrates too many responsibilities
  • src/utils/definition— sits on a dependency cycle
  • src/utils/definition— shared utility hub
  • src/utils/definition— crosses a layer boundary

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 94/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