Skip to main content
ArcSight

← HomepageAll repository proofValidation recordState of TS Architecture 2026

Repository proof

What ArcSight found in Nitro

Real arc impact on Nitro — blast radius, break paths, and evidence. Same question as the homepage: what breaks if I change this?

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

arc impact src/presets/_utils/preset
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/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

What ArcSight found

src/presets/_utils/preset: fan-in 32, blast radius 50, HIGH. 224 modules and 283 dependency edges traced.

Why it matters

In Nitro, Change-risk signal at src/presets/_utils/preset (fan-in 32) — merge impact can travel beyond the diff you see. Blast radius on src/presets/_utils/preset reaches 50 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/presets/_utils/preset
  • src/presets/_utils/fs
  • src/utils/fs

What evidence supports it

  • Local CLI analysis — repository source stays on your machine
  • Structural coverage: 224 modules, 283 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: 92.9/100 · Stability: 36/100 · Status: healthy · Confidence: 100%

  • Dependency cycles: 5
  • Duplicate authorities: 13

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

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…) →

Nitro architecture metrics
Score
92.9
Modules
224
Edges
283

Metrics

MetricValue
Architecture score92.9/100
Modules224
Edges283
Dependency cycles5

FAQ

What did ArcSight find in Nitro?
src/presets/_utils/preset: fan-in 32, blast radius 50, HIGH. 224 modules and 283 dependency edges traced.
Why does the Nitro structure matter?
In Nitro, Change-risk signal at src/presets/_utils/preset (fan-in 32) — merge impact can travel beyond the diff you see. Blast radius on src/presets/_utils/preset reaches 50 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 Nitro?
Start with src/presets/_utils/preset. Run arc impact on that file before the change merges.

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 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/nitro/" width="320" height="180" frameborder="0"></iframe>

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