Skip to main content
ArcSight

← HomepageAll repository proofValidation recordState of TS Architecture 2026

Repository proof

What ArcSight found in Vendure

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

Project: Vendure (packages/cli) · Score: 93.2/100 (Excellent architecture) · 62 modules · 163 edges

arc impact src/constants
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/utilities/ast-utils16 dependents
  • src/shared/vendure-plugin-ref13 dependents
  • src/utilities/utils13 dependents
  • src/shared/shared-prompts13 dependents
  • src/shared/cli-command11 dependents
  • src/constants9 dependents
  • src/shared/vendure-config-ref9 dependents
  • src/shared/entity-ref7 dependents
Blast radius, downstream modules
  • src/constants31 modules
  • src/utilities/ast-utils28 modules
  • src/shared/vendure-plugin-ref23 modules
  • src/utilities/utils21 modules
  • src/shared/cli-command19 modules
  • src/shared/shared-prompts18 modules
  • src/commands/add/service/add-service18 modules
  • src/commands/add/entity/add-entity18 modules
ModuleFan-inBlastRisk
src/constants931MEDIUM
src/utilities/ast-utils1628MEDIUM
src/shared/vendure-plugin-ref1323LOW
src/utilities/utils1321CRITICAL
src/shared/cli-command1119CRITICAL
src/shared/shared-prompts1318CRITICAL
src/commands/add/service/add-service518CRITICAL
src/commands/add/entity/add-entity418CRITICAL
src/shared/vendure-config-ref914CRITICAL
src/commands/schema/schema24HIGH
src/shared/entity-ref7MEDIUM
src/utilities/monorepo-utils2LOW

What ArcSight found

src/constants: fan-in 9, blast radius 31, MEDIUM. 62 modules and 163 dependency edges traced.

Why it matters

In Vendure (packages/cli), Change-risk signal at src/constants (fan-in 9) — merge impact can travel beyond the diff you see. Blast radius on src/constants reaches 31 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/constants
  • src/utilities/ast-utils
  • src/shared/vendure-plugin-ref

What evidence supports it

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

  • Dependency cycles: 4
  • Duplicate authorities: 4

Architectural gravity centers

  • src/utilities/ast-utils— concentrates too many responsibilities
  • src/utilities/ast-utils— shared utility hub
  • src/shared/vendure-plugin-ref— concentrates too many responsibilities
  • src/shared/vendure-plugin-ref— shared utility hub
  • src/utilities/utils— 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…) →

Vendure (packages/cli) architecture metrics
Score
93.2
Modules
62
Edges
163

Metrics

MetricValue
Architecture score93.2/100
Modules62
Edges163
Dependency cycles4

FAQ

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

Key takeaways

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

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