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?

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

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

arc impact src/utils/workspace-root

Install ArcSightRun arc impact in under 3 minutes Why trust ArcSight →

Proof summary

Four questions every public repository page must answer — see validation record · Change Impact problem · Circular Dependencies problem · Blast Radius problem.

What ArcSight found

High-risk module src/utils/workspace-root (fan-in 112) — CRITICAL. src/utils/fileutils: fan-in 71, blast radius 478 modules. src/utils/fileutils — god-module. 589 modules and 2,843 dependency edges traced.

Why it matters

In Nx (packages/nx), Change-risk signal at src/utils/workspace-root (fan-in 112) — 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/workspace-root
src/config/nx-json
src/utils/fileutils

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

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 for this codebase — Dependency graph

Subsystem architecture for this codebase — Subsystem architecture

Architecture score & metrics

Score: 68.5/100 · Stability: 1/100 · Status: at_risk · Confidence: 100%

Dependency cycles: 100
Duplicate authorities: 41

Critical findings

src/utils/workspace-rootCRITICALfan-in: 112
src/config/nx-jsonCRITICALfan-in: 123
src/utils/fileutilsCRITICALfan-in: 71
src/config/project-graphCRITICALfan-in: 105
src/utils/outputCRITICALfan-in: 102

Hotspots

src/utils/fileutilsCRITICALfan-in: 71blast: 478
src/utils/fileutilsHIGHfan-in: 71blast: 478
src/utils/workspace-rootCRITICALfan-in: 112blast: 476
src/utils/workspace-rootHIGHfan-in: 112blast: 476
src/utils/versionsCRITICALfan-in: 21blast: 467
src/utils/versionsHIGHfan-in: 21blast: 467
src/nativeCRITICALfan-in: 64blast: 465
src/nativeHIGHfan-in: 64blast: 465
src/utils/pathCRITICALfan-in: 26blast: 454
src/utils/pathHIGHfan-in: 26blast: 454

Architectural gravity centers

src/utils/fileutils— god-module
src/utils/fileutils— utility-hub
src/utils/workspace-root— god-module
src/utils/workspace-root— utility-hub
src/utils/versions— god-module

CLI workflow

Scan → Fix → Finish → Watch. Nothing else required.

arc scanFind issues
arc fixApply fixes
arc finishResolve remaining
arc watchKeep clean (Pro)

More commands (explain, impact, guard…) →

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 →

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

Change Impact problemCircular Dependencies problemBlast Radius problem

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