Skip to main content
ArcSight

← HomepageAll repository proofValidation recordState 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?

Run the same analysis on your repository in under 3 minutes.

Project: tRPC (packages/server)Score: 79.3/100 (Healthy architecture)76 modules251 edges
arc impact src/unstable-core-do-not-import/utils

Proof summary

Four questions every public repository page must answer — see validation record.

What ArcSight found

High-risk module src/unstable-core-do-not-import/utils (fan-in 17) — HIGH. src/unstable-core-do-not-import/utils: fan-in 17, blast radius 60 modules. src/unstable-core-do-not-import/utils — god-module. 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/stream/utils/disposable

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

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
Dependency graph for this codebase
Subsystem architecture
Subsystem architecture for this codebase
Risk map
Risk map for this codebase

Architecture score & metrics

Score: 79.3/100 · Stability: 29/100 · Status: moderate_risk · Confidence: 100%

  • Dependency cycles: 10
  • Duplicate authorities: 58

Critical findings

  • src/unstable-core-do-not-import/utilsHIGHfan-in: 17
  • src/unstable-core-do-not-import/typesMEDIUMfan-in: 12
  • src/unstable-core-do-not-import/stream/utils/disposableMEDIUMfan-in: 6
  • src/unstable-core-do-not-import/error/TRPCErrorMEDIUMfan-in: 13
  • src/unstable-core-do-not-importMEDIUMfan-in: 13

Hotspots

  • src/unstable-core-do-not-import/utilsCRITICALfan-in: 17blast: 60
  • src/unstable-core-do-not-import/utilsHIGHfan-in: 17blast: 60
  • src/unstable-core-do-not-import/typesCRITICALfan-in: 12blast: 56
  • src/unstable-core-do-not-import/error/TRPCErrorCRITICALfan-in: 13blast: 53
  • src/unstable-core-do-not-import/error/TRPCErrorHIGHfan-in: 13blast: 53
  • src/unstable-core-do-not-importCRITICALfan-in: 13blast: 51
  • src/unstable-core-do-not-importCRITICALfan-in: 13blast: 51
  • src/unstable-core-do-not-importHIGHfan-in: 13blast: 51
  • src/unstable-core-do-not-import/procedureCRITICALfan-in: 13blast: 51
  • src/unstable-core-do-not-import/procedureCRITICALfan-in: 13blast: 51

Architectural gravity centers

  • src/unstable-core-do-not-import/utilsgod-module
  • src/unstable-core-do-not-import/utilsutility-hub
  • src/unstable-core-do-not-import/typesgod-module
  • src/unstable-core-do-not-import/error/TRPCErrorgod-module
  • src/unstable-core-do-not-import/error/TRPCErrorutility-hub

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/trpc/" width="320" height="180" frameborder="0"></iframe>

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