Which file should I inspect first in Directus (api)?

Start with src/utils/get-config-from-env. 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 Directus

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

Project: Directus (api) · Score: 75.1/100 (Healthy architecture) · 789 modules · 2,287 edges

arc impact src/utils/get-config-from-env

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.

High fan-in in Directus

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/logger104 dependents
src/constants34 dependents
src/cache25 dependents
src/utils/get-config-from-env16 dependents
src/bus15 dependents
src/utils/get-milliseconds14 dependents
src/permissions/modules/process-ast/types11 dependents
src/utils/get-default-index-name9 dependents

Blast radius, downstream modules

src/utils/get-config-from-env435 modules
src/bus401 modules
src/logger396 modules
src/utils/get-milliseconds354 modules
src/permissions/modules/process-ast/types350 modules
src/constants345 modules
src/utils/get-default-index-name341 modules
src/cache340 modules

Module	Fan-in	Blast	Risk
src/utils/get-config-from-env	16	435	CRITICAL
src/bus	15	401	CRITICAL
src/logger	104	396	CRITICAL
src/utils/get-milliseconds	14	354	CRITICAL
src/permissions/modules/process-ast/types	11	350	CRITICAL
src/constants	34	345	CRITICAL
src/utils/get-default-index-name	9	341	MEDIUM
src/cache	25	340	CRITICAL
src/redis	8		CRITICAL
src/redis/lib/create-redis	2		CRITICAL
src/redis/lib/use-redis	1		CRITICAL

What ArcSight found

src/utils/get-config-from-env: fan-in 16, blast radius 435, CRITICAL. 789 modules and 2,287 dependency edges traced.

Why it matters

In Directus (api), Change-risk signal at src/utils/get-config-from-env (fan-in 16) — 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/utils/get-config-from-env
src/bus
src/logger

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

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: 75.1/100 · Stability: 1/100 · Status: moderate_risk · Confidence: 100%

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

Architectural gravity centers

src/utils/get-config-from-env— concentrates too many responsibilities
src/utils/get-config-from-env— shared utility hub
src/bus— concentrates too many responsibilities
src/bus— shared utility hub
src/logger— 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…) →

Directus (api) architecture metrics

Score: 75.1
Modules: 789
Edges: 2,287

Metrics

Metric	Value
Architecture score	75.1/100
Modules	789
Edges	2,287
Dependency cycles	100+

FAQ

What did ArcSight find in Directus (api)?: src/utils/get-config-from-env: fan-in 16, blast radius 435, CRITICAL. 789 modules and 2,287 dependency edges traced.
Why does the Directus (api) structure matter?: In Directus (api), Change-risk signal at src/utils/get-config-from-env (fan-in 16) — 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.
Which file should I inspect first in Directus (api)?: Start with src/utils/get-config-from-env. 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/directus/" width="320" height="180" frameborder="0"></iframe>

Explore

High fan-in in DirectusChange Impact definition

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