Which file should I inspect first in Docusaurus (packages/docusaurus)?

Start with src/server/plugins/configs. 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 Docusaurus

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

Project: Docusaurus (packages/docusaurus) · Score: 95.6/100 (Excellent architecture) · 118 modules · 171 edges

arc impact src/server/plugins/configs

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/server/site9 dependents
src/commands/swizzle/common8 dependents
src/server/plugins/init5 dependents
src/commands/swizzle/prompts4 dependents
src/server/plugins/configs3 dependents
src/server/translations/translations3 dependents
src/commands/swizzle/actions3 dependents
src/commands/swizzle/components3 dependents

Blast radius, downstream modules

src/server/plugins/configs24 modules
src/server/plugins/init16 modules
src/server/translations/translations16 modules
src/server/site14 modules
src/server/siteMessages14 modules
src/commands/swizzle/common10 modules
src/commands/swizzle/prompts8 modules
src/commands/swizzle/actions8 modules

Module	Fan-in	Blast	Risk
src/server/plugins/configs	3	24	LOW
src/server/plugins/init	5	16	LOW
src/server/translations/translations	3	16	CRITICAL
src/server/site	9	14	LOW
src/server/siteMessages	1	14	HIGH
src/commands/swizzle/common	8	10	HIGH
src/commands/swizzle/prompts	4	8	CRITICAL
src/commands/swizzle/actions	3	8	CRITICAL
src/commands/swizzle/components	3	8	CRITICAL
src/commands/swizzle/tables	2	8	CRITICAL
src/server/plugins/moduleShorthand	2		LOW
src/server/plugins/presets	1		LOW

What ArcSight found

src/server/plugins/configs: fan-in 3, blast radius 24, LOW. 118 modules and 171 dependency edges traced.

Why it matters

In Docusaurus (packages/docusaurus), Change-risk signal at src/server/plugins/configs (fan-in 3) — merge impact can travel beyond the diff you see. Blast radius on src/server/plugins/configs reaches 24 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/server/plugins/configs
src/server/plugins/init
src/server/translations/translations

What evidence supports it

Local CLI analysis — repository source stays on your machine
Structural coverage: 118 modules, 171 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: 95.6/100 · Stability: 43/100 · Status: healthy · Confidence: 100%

Dependency cycles: 8
Duplicate authorities: 3

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

Docusaurus (packages/docusaurus) architecture metrics

Score: 95.6
Modules: 118
Edges: 171

Metrics

Metric	Value
Architecture score	95.6/100
Modules	118
Edges	171
Dependency cycles	8

FAQ

What did ArcSight find in Docusaurus (packages/docusaurus)?: src/server/plugins/configs: fan-in 3, blast radius 24, LOW. 118 modules and 171 dependency edges traced.
Why does the Docusaurus (packages/docusaurus) structure matter?: In Docusaurus (packages/docusaurus), Change-risk signal at src/server/plugins/configs (fan-in 3) — merge impact can travel beyond the diff you see. Blast radius on src/server/plugins/configs reaches 24 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 Docusaurus (packages/docusaurus)?: Start with src/server/plugins/configs. Run arc impact on that file before the change merges.

Key takeaways

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

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