Skip to main content
ArcSight

← Homepage

Impact analysis example

What breaks when you change Supabase (packages/ui)?

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

Project: Supabase (packages/ui) · Score: 93.9/100 (Excellent architecture) · 159 modules · 185 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 Supabase (packages/ui). 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: 93.9/100 · Stability: 44/100 · Status: healthy · Confidence: 100%

  • Duplicate authorities: 3

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/lib/utils/cn54 dependents
  • src/components/Icon/IconBase20 dependents
  • src/lib/theme/styleHandler8 dependents
  • src/lib/theme/defaultTheme4 dependents
  • src/components/ThemeProvider/ThemeProvider1 dependents
  • src/lib/commonCva1 dependents
  • src/components/Icon/IconContext1 dependents
  • src/lib/utils/clipboard1 dependents
Blast radius, downstream modules
  • src/lib/utils/cn118 modules
  • src/lib/theme/defaultTheme58 modules
  • src/components/ThemeProvider/ThemeProvider54 modules
  • src/lib/theme/styleHandler53 modules
  • src/lib/commonCva42 modules
  • src/components/Icon/IconContext41 modules
  • src/components/Icon/IconBase40 modules
  • src/lib/utils/clipboard18 modules
ModuleFan-inBlastRisk
src/lib/utils/cn54118CRITICAL
src/lib/theme/defaultTheme458MEDIUM
src/components/ThemeProvider/ThemeProvider154MEDIUM
src/lib/theme/styleHandler853MEDIUM
src/lib/commonCva142CRITICAL
src/components/Icon/IconContext141CRITICAL
src/components/Icon/IconBase2040MEDIUM
src/lib/utils/clipboard118HIGH
src/lib/utils/mergeDeep118HIGH
src/lib/utils/randomIdGenerator118HIGH

Architectural gravity centers

  • src/lib/utils/cn— concentrates too many responsibilities
  • src/lib/utils/cn— shared utility hub
  • src/lib/theme/defaultTheme— concentrates too many responsibilities
  • src/components/ThemeProvider/ThemeProvider— concentrates too many responsibilities
  • src/lib/theme/styleHandler— concentrates too many responsibilities

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 93.9/100 indicates a healthy structure with room to reduce cycles and violations.
  • •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