What ArcSight found
src/crypto: fan-in 27, blast radius 148, CRITICAL. 273 modules and 846 dependency edges traced.
← HomepageAll repository proofValidation recordState of TS Architecture 2026
Repository proof
What ArcSight found in Better Auth
Real arc impact on Better Auth (packages/better-auth) — blast radius, break paths, and evidence. Same question as the homepage: what breaks if I change this?
Project: Better Auth (packages/better-auth) · Score: 78.9/100 (Healthy architecture) · 273 modules · 846 edges
arc impact src/cryptoRun 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/types43 dependents
- src/cookies38 dependents
- src/api36 dependents
- src/crypto27 dependents
- src/db/schema23 dependents
- src/types/helper16 dependents
- src/utils/url13 dependents
- src/utils/date11 dependents
- src/crypto148 modules
- src/crypto/jwt148 modules
- src/types/helper147 modules
- src/utils/url147 modules
- src/utils/date145 modules
- src/utils/is-api-error145 modules
- src/types143 modules
- src/cookies143 modules
| Module | Fan-in | Blast | Risk |
|---|---|---|---|
| src/crypto | 27 | 148 | CRITICAL |
| src/crypto/jwt | 3 | 148 | HIGH |
| src/types/helper | 16 | 147 | CRITICAL |
| src/utils/url | 13 | 147 | CRITICAL |
| src/utils/date | 11 | 145 | CRITICAL |
| src/utils/is-api-error | 11 | 145 | CRITICAL |
| src/types | 43 | 143 | CRITICAL |
| src/cookies | 38 | 143 | CRITICAL |
| src/api | 36 | CRITICAL | |
| src/db/schema | 23 | CRITICAL |
Why it matters
In Better Auth (packages/better-auth), Change-risk signal at src/crypto (fan-in 27) — merge impact can travel beyond the diff you see. Blast radius on src/crypto reaches 148 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/crypto
- src/crypto/jwt
- src/types/helper
What evidence supports it
- Local CLI analysis — repository source stays on your machine
- Structural coverage: 273 modules, 846 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: 78.9/100 · Stability: 8/100 · Status: moderate_risk · Confidence: 100%
- Dependency cycles: 27
- Duplicate authorities: 55
Architectural gravity centers
src/crypto— concentrates too many responsibilitiessrc/crypto— shared utility hubsrc/crypto— sits on a dependency cyclesrc/crypto/jwt— sits on a dependency cyclesrc/types/helper— 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
- 78.9
- Modules
- 273
- Edges
- 846
Metrics
| Metric | Value |
|---|---|
| Architecture score | 78.9/100 |
| Modules | 273 |
| Edges | 846 |
| Dependency cycles | 27 |
FAQ
- What did ArcSight find in Better Auth (packages/better-auth)?
- src/crypto: fan-in 27, blast radius 148, CRITICAL. 273 modules and 846 dependency edges traced.
- Why does the Better Auth (packages/better-auth) structure matter?
- In Better Auth (packages/better-auth), Change-risk signal at src/crypto (fan-in 27) — merge impact can travel beyond the diff you see. Blast radius on src/crypto reaches 148 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 Better Auth (packages/better-auth)?
- Start with src/crypto. 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/better-auth/" width="320" height="180" frameborder="0"></iframe>Evidence-backed analysis snapshot. Validation record · Install · Homepage demo