Skip to main content
ArcSight

← HomepageAll repository proofValidation recordState of TS Architecture 2026

Repository proof

What ArcSight found in Nuxt

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

Project: Nuxt (packages/schema) · Score: 94/100 (Excellent architecture) · 35 modules · 84 edges

arc impact src/utils/definition
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/utils/definition18 dependents
  • src/types/nuxt7 dependents
  • src/types/config5 dependents
  • src/types/module5 dependents
  • src/types/components4 dependents
  • src/types/debug4 dependents
  • src/types/head4 dependents
Blast radius, downstream modules
  • src/utils/definition26 modules
  • src/types/nuxt26 modules
  • src/types/config26 modules
  • src/types/module26 modules
  • src/types/components26 modules
  • src/types/debug26 modules
ModuleFan-inBlastRisk
src/utils/definition1826MEDIUM
src/types/nuxt726LOW
src/types/config526LOW
src/types/module526LOW
src/types/components426CRITICAL
src/types/debug426CRITICAL
src/types/head4LOW

What ArcSight found

src/utils/definition: fan-in 18, blast radius 26, MEDIUM. 35 modules and 84 dependency edges traced.

Why it matters

In Nuxt (packages/schema), Change-risk signal at src/utils/definition (fan-in 18) — merge impact can travel beyond the diff you see. Blast radius on src/utils/definition reaches 26 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/utils/definition
  • src/types/nuxt
  • src/types/config

What evidence supports it

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

  • Dependency cycles: 7
  • Layer violations: 2

Architectural gravity centers

  • src/utils/definition— concentrates too many responsibilities
  • src/utils/definition— sits on a dependency cycle
  • src/utils/definition— shared utility hub
  • src/utils/definition— crosses a layer boundary

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

Nuxt (packages/schema) architecture metrics
Score
94
Modules
35
Edges
84

Metrics

MetricValue
Architecture score94/100
Modules35
Edges84
Dependency cycles7

FAQ

What did ArcSight find in Nuxt (packages/schema)?
src/utils/definition: fan-in 18, blast radius 26, MEDIUM. 35 modules and 84 dependency edges traced.
Why does the Nuxt (packages/schema) structure matter?
In Nuxt (packages/schema), Change-risk signal at src/utils/definition (fan-in 18) — merge impact can travel beyond the diff you see. Blast radius on src/utils/definition reaches 26 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 Nuxt (packages/schema)?
Start with src/utils/definition. Run arc impact on that file before the change merges.

Key takeaways

  • •Architecture score 94/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/nuxt/" width="320" height="180" frameborder="0"></iframe>

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