Skip to main content
ArcSight

← HomepageAll repository proofValidation recordState of TS Architecture 2026

Repository proof

What ArcSight found in Medusa

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

Project: Medusa (packages/medusa) · Score: 91/100 (Excellent architecture) · 721 modules · 726 edges

arc impact src/api/utils/validators
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/api/utils/validators80 dependents
  • src/api/utils/common-validators51 dependents
  • src/utils17 dependents
  • src/api/admin/products/helpers13 dependents
  • src/loaders12 dependents
  • src/feature-flags/translation11 dependents
  • src/api/admin/returns/query-config11 dependents
  • src/commands/utils/dev-server/types9 dependents
Blast radius, downstream modules
  • src/api/utils/validators197 modules
  • src/api/utils/common-validators151 modules
  • src/utils/middlewares/authenticate-middleware44 modules
  • src/utils33 modules
  • src/feature-flags/translation17 modules
  • src/api/admin/products/validators17 modules
  • src/feature-flags/rbac16 modules
  • src/loaders15 modules
ModuleFan-inBlastRisk
src/api/utils/validators80197CRITICAL
src/api/utils/common-validators51151CRITICAL
src/utils/middlewares/authenticate-middleware544MEDIUM
src/utils1733HIGH
src/feature-flags/translation1117HIGH
src/api/admin/products/validators317HIGH
src/feature-flags/rbac816HIGH
src/loaders1215HIGH
src/api/store/types514HIGH
src/api/admin/products/helpers1313HIGH
src/commands/utils/dev-server/types913HIGH
src/api/admin/returns/query-config1112HIGH
src/commands/utils/dev-server/module-cache-manager812HIGH
src/api/auth/validators910HIGH
src/api/utils/common-validators/common2CRITICAL
src/api/utils/common-validators/products1CRITICAL

What ArcSight found

src/api/utils/validators: fan-in 80, blast radius 197, CRITICAL. 721 modules and 726 dependency edges traced.

Why it matters

In Medusa (packages/medusa), Change-risk signal at src/api/utils/validators (fan-in 80) — merge impact can travel beyond the diff you see. Blast radius on src/api/utils/validators reaches 197 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/api/utils/validators
  • src/api/utils/common-validators
  • src/utils/middlewares/authenticate-middleware

What evidence supports it

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

  • Dependency cycles: 1
  • Duplicate authorities: 32

Architectural gravity centers

  • src/api/utils/validators— concentrates too many responsibilities
  • src/api/utils/validators— shared utility hub
  • src/api/utils/common-validators— concentrates too many responsibilities
  • src/utils— depends on an unstable module
  • src/feature-flags/translation— shared utility hub

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

Medusa (packages/medusa) architecture metrics
Score
91
Modules
721
Edges
726

Metrics

MetricValue
Architecture score91/100
Modules721
Edges726
Dependency cycles1

FAQ

What did ArcSight find in Medusa (packages/medusa)?
src/api/utils/validators: fan-in 80, blast radius 197, CRITICAL. 721 modules and 726 dependency edges traced.
Why does the Medusa (packages/medusa) structure matter?
In Medusa (packages/medusa), Change-risk signal at src/api/utils/validators (fan-in 80) — merge impact can travel beyond the diff you see. Blast radius on src/api/utils/validators reaches 197 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 Medusa (packages/medusa)?
Start with src/api/utils/validators. Run arc impact on that file before the change merges.

Key takeaways

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

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