Which file should I inspect first in tRPC (packages/server)?

Start with src/unstable-core-do-not-import/utils. 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 tRPC

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

Project: tRPC (packages/server) · Score: 79.3/100 (Healthy architecture) · 76 modules · 251 edges

arc impact src/unstable-core-do-not-import/utils

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/unstable-core-do-not-import/utils17 dependents
src/unstable-core-do-not-import/error/TRPCError13 dependents
src/unstable-core-do-not-import13 dependents
src/unstable-core-do-not-import/procedure13 dependents
src/unstable-core-do-not-import/types12 dependents
src/unstable-core-do-not-import/router7 dependents
src/unstable-core-do-not-import/rpc7 dependents
src/unstable-core-do-not-import/stream/utils/disposable6 dependents

Blast radius, downstream modules

src/unstable-core-do-not-import/utils60 modules
src/unstable-core-do-not-import/types56 modules
src/unstable-core-do-not-import/error/TRPCError53 modules
src/unstable-core-do-not-import51 modules
src/unstable-core-do-not-import/procedure51 modules
src/unstable-core-do-not-import/router51 modules
src/unstable-core-do-not-import/rpc51 modules

Module	Fan-in	Blast	Risk
src/unstable-core-do-not-import/utils	17	60	HIGH
src/unstable-core-do-not-import/types	12	56	MEDIUM
src/unstable-core-do-not-import/error/TRPCError	13	53	MEDIUM
src/unstable-core-do-not-import	13	51	MEDIUM
src/unstable-core-do-not-import/procedure	13	51	CRITICAL
src/unstable-core-do-not-import/router	7	51	CRITICAL
src/unstable-core-do-not-import/rpc	7	51	CRITICAL
src/unstable-core-do-not-import/stream/utils/disposable	6		MEDIUM

What ArcSight found

src/unstable-core-do-not-import/utils: fan-in 17, blast radius 60, HIGH. 76 modules and 251 dependency edges traced.

Why it matters

In tRPC (packages/server), Change-risk signal at src/unstable-core-do-not-import/utils (fan-in 17) — merge impact can travel beyond the diff you see. Blast radius on src/unstable-core-do-not-import/utils reaches 60 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/unstable-core-do-not-import/utils
src/unstable-core-do-not-import/types
src/unstable-core-do-not-import/error/TRPCError

What evidence supports it

Local CLI analysis — repository source stays on your machine
Structural coverage: 76 modules, 251 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: 79.3/100 · Stability: 29/100 · Status: moderate_risk · Confidence: 100%

Dependency cycles: 10
Duplicate authorities: 58

Architectural gravity centers

src/unstable-core-do-not-import/utils— concentrates too many responsibilities
src/unstable-core-do-not-import/utils— shared utility hub
src/unstable-core-do-not-import/types— concentrates too many responsibilities
src/unstable-core-do-not-import/error/TRPCError— concentrates too many responsibilities
src/unstable-core-do-not-import/error/TRPCError— shared utility hub

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

tRPC (packages/server) architecture metrics

Score: 79.3
Modules: 76
Edges: 251

Metrics

Metric	Value
Architecture score	79.3/100
Modules	76
Edges	251
Dependency cycles	10

FAQ

What did ArcSight find in tRPC (packages/server)?: src/unstable-core-do-not-import/utils: fan-in 17, blast radius 60, HIGH. 76 modules and 251 dependency edges traced.
Why does the tRPC (packages/server) structure matter?: In tRPC (packages/server), Change-risk signal at src/unstable-core-do-not-import/utils (fan-in 17) — merge impact can travel beyond the diff you see. Blast radius on src/unstable-core-do-not-import/utils reaches 60 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 tRPC (packages/server)?: Start with src/unstable-core-do-not-import/utils. 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/trpc/" width="320" height="180" frameborder="0"></iframe>

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