Which file should I inspect first in Payload CMS (packages/payload)?

Start with src/errors/APIError. Run arc impact on that file before the change merges.

← Homepage All repository proof Validation record State of TS Architecture 2026

Repository proof

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?

Project: Payload CMS (packages/payload) · Score: 71.1/100 (Moderate technical debt) · 627 modules · 2,704 edges

arc impact src/errors/APIError

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.

Circular dependencies in Payload CMS · High fan-in in Payload CMS

Definitions: Change Impact definition

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/types225 dependents
src154 dependents
src/config/types142 dependents
src/collections/config/types128 dependents
src/fields/config/types124 dependents
src/errors/APIError41 dependents
src/versions/types16 dependents
src/utilities/isNumber14 dependents

Blast radius, downstream modules

src/errors/APIError495 modules
src/versions/types477 modules
src/utilities/isNumber477 modules
src/types476 modules
src476 modules
src/config/types476 modules

Module	Fan-in	Blast	Risk
src/errors/APIError	41	495	CRITICAL
src/versions/types	16	477	CRITICAL
src/utilities/isNumber	14	477	CRITICAL
src/types	225	476	CRITICAL
src	154	476	CRITICAL
src/config/types	142	476	CRITICAL
src/collections/config/types	128		CRITICAL
src/fields/config/types	124		CRITICAL

What ArcSight found

src/errors/APIError: fan-in 41, blast radius 495, CRITICAL. 627 modules and 2,704 dependency edges traced.

Why it matters

In Payload CMS (packages/payload), Change-risk signal at src/errors/APIError (fan-in 41) — 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/errors/APIError
src/versions/types
src/utilities/isNumber

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

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

Architectural gravity centers

src/errors/APIError— concentrates too many responsibilities
src/errors/APIError— shared utility hub
src/versions/types— concentrates too many responsibilities
src/versions/types— shared utility hub
src/utilities/isNumber— 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…) →

Payload CMS (packages/payload) architecture metrics

Score: 71.1
Modules: 627
Edges: 2,704

Metrics

Metric	Value
Architecture score	71.1/100
Modules	627
Edges	2,704
Dependency cycles	100+

FAQ

What did ArcSight find in Payload CMS (packages/payload)?: src/errors/APIError: fan-in 41, blast radius 495, CRITICAL. 627 modules and 2,704 dependency edges traced.
Why does the Payload CMS (packages/payload) structure matter?: In Payload CMS (packages/payload), Change-risk signal at src/errors/APIError (fan-in 41) — 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.
Which file should I inspect first in Payload CMS (packages/payload)?: Start with src/errors/APIError. Run arc impact on that file before the change merges.

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

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

Circular dependencies in Payload CMSHigh fan-in in Payload CMSChange Impact definition

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