Skip to main content
ArcSight

← HomepageAll repository proofValidation recordState of TS Architecture 2026

Repository proof

What ArcSight found in Nx

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

Project: Nx (packages/nx) · Score: 68.5/100 (Moderate technical debt) · 589 modules · 2,843 edges

arc impact src/utils/fileutils
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.

Circular dependencies in Nx · Blast radius in Nx

Definitions: Change Impact definition

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/config/nx-json123 dependents
  • src/utils/workspace-root112 dependents
  • src/config/project-graph105 dependents
  • src/utils/output102 dependents
  • src/utils/fileutils71 dependents
  • src/native64 dependents
  • src/config/task-graph38 dependents
  • src/utils/path26 dependents
Blast radius, downstream modules
  • src/utils/fileutils478 modules
  • src/utils/workspace-root476 modules
  • src/utils/versions467 modules
  • src/native465 modules
  • src/utils/path454 modules
  • src/config/task-graph453 modules
  • src/config/nx-json452 modules
ModuleFan-inBlastRisk
src/utils/fileutils71478CRITICAL
src/utils/workspace-root112476CRITICAL
src/utils/versions21467CRITICAL
src/native64465CRITICAL
src/utils/path26454CRITICAL
src/config/task-graph38453CRITICAL
src/config/nx-json123452CRITICAL
src/config/project-graph105CRITICAL
src/utils/output102CRITICAL

What ArcSight found

src/utils/fileutils: fan-in 71, blast radius 478, CRITICAL. 589 modules and 2,843 dependency edges traced.

Why it matters

In Nx (packages/nx), Change-risk signal at src/utils/fileutils (fan-in 71) — merge impact can travel beyond the diff you see. Blast radius on src/utils/fileutils reaches 478 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/fileutils
  • src/utils/workspace-root
  • src/utils/versions

What evidence supports it

  • Local CLI analysis — repository source stays on your machine
  • Structural coverage: 589 modules, 2,843 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: 68.5/100 · Stability: 1/100 · Status: at_risk · Confidence: 100%

  • Dependency cycles: 100+
  • Duplicate authorities: 41

Architectural gravity centers

  • src/utils/fileutils— concentrates too many responsibilities
  • src/utils/fileutils— shared utility hub
  • src/utils/workspace-root— concentrates too many responsibilities
  • src/utils/workspace-root— shared utility hub
  • src/utils/versions— concentrates too many responsibilities

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

Nx (packages/nx) architecture metrics
Score
68.5
Modules
589
Edges
2,843

Metrics

MetricValue
Architecture score68.5/100
Modules589
Edges2,843
Dependency cycles100+

FAQ

What did ArcSight find in Nx (packages/nx)?
src/utils/fileutils: fan-in 71, blast radius 478, CRITICAL. 589 modules and 2,843 dependency edges traced.
Why does the Nx (packages/nx) structure matter?
In Nx (packages/nx), Change-risk signal at src/utils/fileutils (fan-in 71) — merge impact can travel beyond the diff you see. Blast radius on src/utils/fileutils reaches 478 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 Nx (packages/nx)?
Start with src/utils/fileutils. Run arc impact on that file before the change merges.

Key takeaways

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

Explore

Circular dependencies in NxBlast radius in NxChange Impact definition

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