What ArcSight found in Directus

Real arc impact on Directus (api) — 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: Directus (api)Score: 75.1/100 (Healthy architecture)789 modules2,287 edges

arc impact src/logger

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

What ArcSight found

High-risk module src/logger (fan-in 104) — CRITICAL. src/utils/get-config-from-env: fan-in 16, blast radius 435 modules. src/utils/get-config-from-env — god-module. 789 modules and 2,287 dependency edges traced.

Why it matters

In Directus (api), Change-risk signal at src/logger (fan-in 104) — merge impact can travel beyond the diff you see. Blast radius on src/utils/get-config-from-env reaches 435 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/logger
src/utils/get-config-from-env
src/redis

What evidence supports it

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

Dependency cycles: 100
Layer violations: 40
Duplicate authorities: 18

Critical findings

src/loggerCRITICALfan-in: 104
src/utils/get-config-from-envCRITICALfan-in: 16
src/redisCRITICALfan-in: 8
src/redis/lib/create-redisCRITICALfan-in: 2
src/redis/lib/use-redisCRITICALfan-in: 1

Hotspots

src/utils/get-config-from-envCRITICALfan-in: 16blast: 435
src/utils/get-config-from-envHIGHfan-in: 16blast: 435
src/busCRITICALfan-in: 15blast: 401
src/busHIGHfan-in: 15blast: 401
src/loggerCRITICALfan-in: 104blast: 396
src/loggerHIGHfan-in: 104blast: 396
src/utils/get-millisecondsCRITICALfan-in: 14blast: 354
src/utils/get-millisecondsHIGHfan-in: 14blast: 354
src/permissions/modules/process-ast/typesCRITICALfan-in: 11blast: 350
src/permissions/modules/process-ast/typesHIGHfan-in: 11blast: 350

Architectural gravity centers

src/utils/get-config-from-env— god-module
src/utils/get-config-from-env— utility-hub
src/bus— god-module
src/bus— utility-hub
src/logger— 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/directus/" width="320" height="180" frameborder="0"></iframe>

Explore

Change Impact problemHigh Fan-In problem

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