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?

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

Project: Medusa (packages/medusa)Score: 91/100 (Excellent architecture)721 modules726 edges

arc impact src/api/utils/validators

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

Proof summary

Four questions every public repository page must answer — see validation record.

What ArcSight found

High-risk module src/api/utils/validators (fan-in 80) — CRITICAL. src/api/utils/validators: fan-in 80, blast radius 197 modules. src/api/utils/validators — god-module. 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/api/utils/common-validators/common

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

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: 91/100 · Stability: 34/100 · Status: healthy · Confidence: 100%

Dependency cycles: 1
Duplicate authorities: 32

Critical findings

src/api/utils/validatorsCRITICALfan-in: 80
src/api/utils/common-validatorsCRITICALfan-in: 51
src/api/utils/common-validators/commonCRITICALfan-in: 2
src/api/utils/common-validators/productsCRITICALfan-in: 1
src/utils/middlewares/authenticate-middlewareMEDIUMfan-in: 5

Hotspots

src/api/utils/validatorsCRITICALfan-in: 80blast: 197
src/api/utils/validatorsHIGHfan-in: 80blast: 197
src/api/utils/common-validatorsCRITICALfan-in: 51blast: 151
src/utils/middlewares/authenticate-middlewareHIGHfan-in: 5blast: 44
src/utilsHIGHfan-in: 17blast: 33
src/feature-flags/translationHIGHfan-in: 11blast: 17
src/api/admin/products/validatorsHIGHfan-in: 3blast: 17
src/feature-flags/rbacHIGHfan-in: 8blast: 16
src/loadersHIGHfan-in: 12blast: 15
src/api/store/typesHIGHfan-in: 5blast: 14

Architectural gravity centers

src/api/utils/validators— god-module
src/api/utils/validators— utility-hub
src/api/utils/common-validators— god-module
src/utils— unstable-dependency
src/feature-flags/translation— utility-hub

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

•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 →

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