Skip to main content
ArcSight

← HomepageAll repository proofValidation recordState of TS Architecture 2026

Repository proof

What ArcSight found in Remix

Real arc impact on Remix (packages/remix) — blast radius, break paths, and evidence. Same question as the homepage: what breaks if I change this?

Project: Remix (packages/remix) · Score: 99.9/100 (Excellent architecture) · 102 modules · 1 edges

arc impact src/cli
Install ArcSight →Why trust ArcSight →

Run the same analysis on your repository in under 3 minutes.

Proof summary

Four questions every public repository page must answer — see validation record.

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

What ArcSight found

src/cli: fan-in 1, blast radius 1, LOW. 102 modules and 1 dependency edges traced.

Why it matters

In Remix (packages/remix), Change-risk signal at src/cli (fan-in 1) — merge impact can travel beyond the diff you see. Blast radius on src/cli reaches 1 downstream modules. ArcSight answers “what breaks if I change this?” before you ship; high fan-in is a change-risk signal, not a verdict on design quality.

What we'd inspect first

  • src/cli
  • src/assert
  • src/assets

What evidence supports it

  • Local CLI analysis — repository source stays on your machine
  • Structural coverage: 102 modules, 1 edges in this snapshot
  • Reproducible fields match homepage live demo and frozen proof output

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%

    CLI workflow

    Impact, then scan, fix, finish, and watch.

    • arc impact <file>See what a change breaks
    • arc scanFind issues
    • arc fixApply fixes
    • arc finishResolve remaining
    • arc watchKeep clean

    More commands (explain, guard…) →

    Remix (packages/remix) architecture metrics
    Score
    99.9
    Modules
    102
    Edges
    1

    Metrics

    MetricValue
    Architecture score99.9/100
    Modules102
    Edges1

    FAQ

    What did ArcSight find in Remix (packages/remix)?
    src/cli: fan-in 1, blast radius 1, LOW. 102 modules and 1 dependency edges traced.
    Why does the Remix (packages/remix) structure matter?
    In Remix (packages/remix), Change-risk signal at src/cli (fan-in 1) — merge impact can travel beyond the diff you see. Blast radius on src/cli reaches 1 downstream modules. ArcSight answers “what breaks if I change this?” before you ship; high fan-in is a change-risk signal, not a verdict on design quality.
    Which file should I inspect first in Remix (packages/remix)?
    Start with src/cli. Run arc impact on that file before the change merges.

    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 locally, then run arc impact on the file you plan to change — before merge.

    npm install -g arcsight
    arc impact <path>
    Install ArcSight →

    Embed this report

    Use this iframe to show the architecture badge on your site.

    <iframe src="https://arcsight.ai/embed/remix/" width="320" height="180" frameborder="0"></iframe>

    Evidence-backed analysis snapshot. Validation record · Install · Homepage demo