Skip to main content
ArcSight

← Homepage

Impact analysis example

What breaks when you change Remix (packages/remix)?

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

Project: Remix (packages/remix) · Score: 99.9/100 (Excellent architecture) · 102 modules · 1 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 Remix (packages/remix). 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: 99.9/100 · Stability: 97/100 · Status: healthy · Confidence: 100%

    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/cli1 dependents
    Blast radius, downstream modules
    • src/cli1 modules
    ModuleFan-inBlastRisk
    src/cli11LOW
    src/assert00LOW
    src/assets00LOW
    src/async-context-middleware00LOW
    src/auth00LOW
    src/auth-middleware00HIGH
    src/cli-entry00HIGH
    src/compression-middleware00HIGH
    src/cookie00HIGH
    src/cop-middleware00HIGH
    src/cors-middleware00HIGH
    src/csrf-middleware00HIGH
    src/data-schema00HIGH
    src/data-schema/checks00HIGH
    src/data-schema/coerce00HIGH

    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 99.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