Skip to main content
ArcSight

← HomepageAll repository proofValidation recordState of TS Architecture 2026

Repository proof

What ArcSight found in Prisma

Real arc impact on Prisma (packages/client) — 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: Prisma (packages/client)Score: 87.1/100 (Healthy architecture)166 modules390 edges
arc impact src/runtime/core/engines/common/types/Transaction

Proof summary

Four questions every public repository page must answer — see validation record · Change Impact problem.

What ArcSight found

High-risk module src/runtime/core/engines/common/types/Transaction (fan-in 8) — MEDIUM. src/runtime/core/engines/common/types/Transaction: fan-in 8, blast radius 47 modules. src/runtime/core/errorRendering/base — god-module. 166 modules and 390 dependency edges traced.

Why it matters

In Prisma (packages/client), Change-risk signal at src/runtime/core/engines/common/types/Transaction (fan-in 8) — merge impact can travel beyond the diff you see. Blast radius on src/runtime/core/engines/common/types/Transaction reaches 47 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/runtime/core/engines/common/types/Transaction
  • src/runtime/core/engines/common/Engine
  • src/runtime/core/engines/common/types/Events

What evidence supports it

  • Local CLI analysis — repository source stays on your machine
  • Structural coverage: 166 modules, 390 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: 87.1/100 · Stability: 24/100 · Status: healthy · Confidence: 100%

  • Dependency cycles: 31
  • Duplicate authorities: 5

Critical findings

  • src/runtime/core/engines/common/types/TransactionMEDIUMfan-in: 8
  • src/runtime/core/engines/common/EngineMEDIUMfan-in: 9
  • src/runtime/core/engines/common/types/EventsMEDIUMfan-in: 5
  • src/runtime/core/engines/common/types/RequestErrorMEDIUMfan-in: 2
  • src/runtime/core/engines/common/types/QueryEngineMEDIUMfan-in: 4

Hotspots

  • src/runtime/core/engines/common/types/TransactionCRITICALfan-in: 8blast: 47
  • src/runtime/core/engines/common/types/TransactionHIGHfan-in: 8blast: 47
  • src/runtime/core/engines/common/EngineCRITICALfan-in: 9blast: 45
  • src/runtime/core/engines/common/EngineHIGHfan-in: 9blast: 45
  • src/runtime/core/types/exported/UtilsCRITICALfan-in: 7blast: 42
  • src/runtime/core/types/exported/UtilsCRITICALfan-in: 7blast: 42
  • src/runtime/core/types/exported/UtilsHIGHfan-in: 7blast: 42
  • src/runtime/core/types/exported/PublicCRITICALfan-in: 6blast: 42
  • src/runtime/core/types/exported/PublicCRITICALfan-in: 6blast: 42
  • src/runtime/core/types/exported/ResultCRITICALfan-in: 4blast: 42

Architectural gravity centers

  • src/runtime/core/errorRendering/basegod-module
  • src/runtime/core/errorRendering/baseutility-hub
  • src/runtime/core/types/exported/JsApigod-module
  • src/runtime/core/types/exported/JsApiutility-hub
  • src/runtime/core/enginesgod-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

  • Architecture score 87.1/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 →

Embed this report

Use this iframe to show the architecture badge on your site.

<iframe src="https://arcsight.ai/embed/prisma/" width="320" height="180" frameborder="0"></iframe>

Explore

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