What ArcSight found
src/runtime/core/engines/common/types/Transaction: fan-in 8, blast radius 47, MEDIUM. 166 modules and 390 dependency edges traced.
← 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?
Project: Prisma (packages/client) · Score: 87.1/100 (Healthy architecture) · 166 modules · 390 edges
arc impact src/runtime/core/engines/common/types/TransactionRun 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.
- src/runtime/core/types/exported/JsApi16 dependents
- src/runtime/core/errorRendering/base12 dependents
- src/runtime/core/engines/common/Engine9 dependents
- src/runtime/core/engines/common/types/Transaction8 dependents
- src/runtime/core/types/exported/Utils7 dependents
- src/runtime/core/types/exported/Public6 dependents
- src/runtime/core/types/exported/TypedSql6 dependents
- src/runtime/core/engines/common/types/Events5 dependents
- src/runtime/core/engines/common/types/Transaction47 modules
- src/runtime/core/engines/common/Engine45 modules
- src/runtime/core/types/exported/Utils42 modules
- src/runtime/core/types/exported/Public42 modules
- src/runtime/core/types/exported/Result42 modules
- src/runtime/core/errorRendering/base39 modules
- src/runtime/core/types/exported/JsApi38 modules
- src/runtime/core/types/exported/TypedSql37 modules
| Module | Fan-in | Blast | Risk |
|---|---|---|---|
| src/runtime/core/engines/common/types/Transaction | 8 | 47 | MEDIUM |
| src/runtime/core/engines/common/Engine | 9 | 45 | MEDIUM |
| src/runtime/core/types/exported/Utils | 7 | 42 | CRITICAL |
| src/runtime/core/types/exported/Public | 6 | 42 | CRITICAL |
| src/runtime/core/types/exported/Result | 4 | 42 | CRITICAL |
| src/runtime/core/errorRendering/base | 12 | 39 | CRITICAL |
| src/runtime/core/types/exported/JsApi | 16 | 38 | CRITICAL |
| src/runtime/core/types/exported/TypedSql | 6 | 37 | CRITICAL |
| src/runtime/core/engines/common/types/Events | 5 | MEDIUM | |
| src/runtime/core/engines/common/types/QueryEngine | 4 | MEDIUM | |
| src/runtime/core/engines/common/types/RequestError | 2 | MEDIUM |
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/types/exported/Utils
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
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.
Architecture score & metrics
Score: 87.1/100 · Stability: 24/100 · Status: healthy · Confidence: 100%
- Dependency cycles: 31
- Duplicate authorities: 5
Architectural gravity centers
src/runtime/core/errorRendering/base— concentrates too many responsibilitiessrc/runtime/core/errorRendering/base— shared utility hubsrc/runtime/core/types/exported/JsApi— concentrates too many responsibilitiessrc/runtime/core/types/exported/JsApi— shared utility hubsrc/runtime/core/engines— concentrates too many responsibilities
CLI workflow
Impact, then scan, fix, finish, and watch.
arc impact <file>See what a change breaksarc scanFind issuesarc fixApply fixesarc finishResolve remainingarc watchKeep clean
- Score
- 87.1
- Modules
- 166
- Edges
- 390
Metrics
| Metric | Value |
|---|---|
| Architecture score | 87.1/100 |
| Modules | 166 |
| Edges | 390 |
| Dependency cycles | 31 |
FAQ
- What did ArcSight find in Prisma (packages/client)?
- src/runtime/core/engines/common/types/Transaction: fan-in 8, blast radius 47, MEDIUM. 166 modules and 390 dependency edges traced.
- Why does the Prisma (packages/client) structure matter?
- 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.
- Which file should I inspect first in Prisma (packages/client)?
- Start with src/runtime/core/engines/common/types/Transaction. Run arc impact on that file before the change merges.
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.
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