What ArcSight found in Payload CMS

Real arc impact on Payload CMS (packages/payload) — 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: Payload CMS (packages/payload)Score: 71.1/100 (Moderate technical debt)627 modules2,704 edges

arc impact src/types

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 · High Fan-In problem.

What ArcSight found

High-risk module src/types (fan-in 225) — CRITICAL. src/errors/APIError: fan-in 41, blast radius 495 modules. src/errors/APIError — god-module. 627 modules and 2,704 dependency edges traced.

Why it matters

In Payload CMS (packages/payload), Change-risk signal at src/types (fan-in 225) — merge impact can travel beyond the diff you see. Blast radius on src/errors/APIError reaches 495 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/types
src
src/config/types

What evidence supports it

Local CLI analysis — repository source stays on your machine
Structural coverage: 627 modules, 2,704 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: 71.1/100 · Stability: 0/100 · Status: moderate_risk · Confidence: 100%

Dependency cycles: 100
Duplicate authorities: 19

Critical findings

src/typesCRITICALfan-in: 225
srcCRITICALfan-in: 154
src/config/typesCRITICALfan-in: 142
src/collections/config/typesCRITICALfan-in: 128
src/fields/config/typesCRITICALfan-in: 124

Hotspots

src/errors/APIErrorCRITICALfan-in: 41blast: 495
src/errors/APIErrorHIGHfan-in: 41blast: 495
src/versions/typesCRITICALfan-in: 16blast: 477
src/versions/typesHIGHfan-in: 16blast: 477
src/utilities/isNumberCRITICALfan-in: 14blast: 477
src/utilities/isNumberHIGHfan-in: 14blast: 477
src/typesCRITICALfan-in: 225blast: 476
src/typesCRITICALfan-in: 225blast: 476
src/typesHIGHfan-in: 225blast: 476
srcCRITICALfan-in: 154blast: 476

Architectural gravity centers

src/errors/APIError— god-module
src/errors/APIError— utility-hub
src/versions/types— god-module
src/versions/types— utility-hub
src/utilities/isNumber— 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/payload/" width="320" height="180" frameborder="0"></iframe>

Explore

Change Impact problemCircular Dependencies problemHigh Fan-In problem

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