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

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

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

Try it in the terminal

Simulated arc analyze output from the dataset. No analysis runs in the browser.

ArcSight CLI (simulated)
$ arc scan nitro
Architecture Score: 92.9
Modules: 224
Cycles: 5
Hotspots: 15

Simulated from dataset. No analysis is run in the browser.

Similar architectures

Repositories with the same language and category, ordered by similar complexity and size.

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?
Nitro has 224 modules and an architecture score of 92.9/100.
Why does the Nitro structure matter?
The Nitro score is 92.9/100 across 224 modules and 283 edges.
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>

Explore

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