What ArcSight found
src/entity: fan-in 308, blast radius 431, CRITICAL. 447 modules and 3,044 dependency edges traced.
← HomepageAll repository proofValidation recordState of TS Architecture 2026
Repository proof
What ArcSight found in Drizzle ORM
Real arc impact on Drizzle ORM (drizzle-orm) — blast radius, break paths, and evidence. Same question as the homepage: what breaks if I change this?
Project: Drizzle ORM (drizzle-orm) · Score: 49.9/100 (High architecture risk) · 447 modules · 3,044 edges
arc impact src/entityRun 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/entity308 dependents
- src/utils194 dependents
- src/sql/sql168 dependents
- src/column147 dependents
- src/column-builder134 dependents
- src/logger62 dependents
- src/cache/core/types39 dependents
- src/query-promise32 dependents
- src/entity431 modules
- src/logger424 modules
- src/cache/core/types424 modules
- src/query-promise424 modules
- src/migrator424 modules
- src/utils423 modules
- src/sql/sql423 modules
| Module | Fan-in | Blast | Risk |
|---|---|---|---|
| src/entity | 308 | 431 | CRITICAL |
| src/logger | 62 | 424 | CRITICAL |
| src/cache/core/types | 39 | 424 | CRITICAL |
| src/query-promise | 32 | 424 | CRITICAL |
| src/migrator | 30 | 424 | CRITICAL |
| src/utils | 194 | 423 | CRITICAL |
| src/sql/sql | 168 | 423 | CRITICAL |
| src/column | 147 | CRITICAL | |
| src/column-builder | 134 | CRITICAL |
Why it matters
In Drizzle ORM (drizzle-orm), Change-risk signal at src/entity (fan-in 308) — merge impact can travel beyond the diff you see. Blast radius on src/entity reaches 431 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/entity
- src/logger
- src/cache/core/types
What evidence supports it
- Local CLI analysis — repository source stays on your machine
- Structural coverage: 447 modules, 3,044 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: 49.9/100 · Stability: 0/100 · Status: critical · Confidence: 100%
- Dependency cycles: 100+
- Duplicate authorities: 226
Architectural gravity centers
src/entity— concentrates too many responsibilitiessrc/entity— shared utility hubsrc/logger— concentrates too many responsibilitiessrc/logger— shared utility hubsrc/cache/core/types— 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
- 49.9
- Modules
- 447
- Edges
- 3,044
Metrics
| Metric | Value |
|---|---|
| Architecture score | 49.9/100 |
| Modules | 447 |
| Edges | 3,044 |
| Dependency cycles | 100+ |
FAQ
- What did ArcSight find in Drizzle ORM (drizzle-orm)?
- src/entity: fan-in 308, blast radius 431, CRITICAL. 447 modules and 3,044 dependency edges traced.
- Why does the Drizzle ORM (drizzle-orm) structure matter?
- In Drizzle ORM (drizzle-orm), Change-risk signal at src/entity (fan-in 308) — merge impact can travel beyond the diff you see. Blast radius on src/entity reaches 431 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 Drizzle ORM (drizzle-orm)?
- Start with src/entity. 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.
Embed this report
Use this iframe to show the architecture badge on your site.
<iframe src="https://arcsight.ai/embed/drizzle/" width="320" height="180" frameborder="0"></iframe>Evidence-backed analysis snapshot. Validation record · Install · Homepage demo