What ArcSight found
src/utils/types: fan-in 9, blast radius 134, CRITICAL. 185 modules and 481 dependency edges traced.
← HomepageAll repository proofValidation recordState of TS Architecture 2026
Repository proof
What ArcSight found in Hono
Real arc impact on Hono — blast radius, break paths, and evidence. Same question as the homepage: what breaks if I change this?
Project: Hono · Score: 84.5/100 (Healthy architecture) · 185 modules · 481 edges
arc impact src/utils/typesRun 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/types52 dependents
- src/context39 dependents
- src/router14 dependents
- src/utils/html13 dependents
- src/http-exception12 dependents
- src/utils/types9 dependents
- src/utils/url9 dependents
- src/utils/http-status8 dependents
- src/utils/types134 modules
- src/utils/html132 modules
- src/router120 modules
- src/utils/url116 modules
- src/utils/http-status109 modules
- src/http-exception108 modules
- src/utils/headers108 modules
- src/types106 modules
| Module | Fan-in | Blast | Risk |
|---|---|---|---|
| src/utils/types | 9 | 134 | CRITICAL |
| src/utils/html | 13 | 132 | CRITICAL |
| src/router | 14 | 120 | CRITICAL |
| src/utils/url | 9 | 116 | CRITICAL |
| src/utils/http-status | 8 | 109 | CRITICAL |
| src/http-exception | 12 | 108 | CRITICAL |
| src/utils/headers | 5 | 108 | MEDIUM |
| src/types | 52 | 106 | CRITICAL |
| src/context | 39 | CRITICAL | |
| src/utils/mime | 4 | CRITICAL |
Why it matters
In Hono, Change-risk signal at src/utils/types (fan-in 9) — merge impact can travel beyond the diff you see. Blast radius on src/utils/types reaches 134 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/utils/types
- src/utils/html
- src/router
What evidence supports it
- Local CLI analysis — repository source stays on your machine
- Structural coverage: 185 modules, 481 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: 84.5/100 · Stability: 10/100 · Status: healthy · Confidence: 100%
- Dependency cycles: 22
- Layer violations: 5
- Duplicate authorities: 8
Architectural gravity centers
src/utils/types— concentrates too many responsibilitiessrc/utils/types— crosses a layer boundarysrc/utils/html— concentrates too many responsibilitiessrc/utils/html— shared utility hubsrc/router— 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
- 84.5
- Modules
- 185
- Edges
- 481
Metrics
| Metric | Value |
|---|---|
| Architecture score | 84.5/100 |
| Modules | 185 |
| Edges | 481 |
| Dependency cycles | 22 |
FAQ
- What did ArcSight find in Hono?
- src/utils/types: fan-in 9, blast radius 134, CRITICAL. 185 modules and 481 dependency edges traced.
- Why does the Hono structure matter?
- In Hono, Change-risk signal at src/utils/types (fan-in 9) — merge impact can travel beyond the diff you see. Blast radius on src/utils/types reaches 134 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 Hono?
- Start with src/utils/types. Run arc impact on that file before the change merges.
Key takeaways
- •Architecture score 84.5/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/hono/" width="320" height="180" frameborder="0"></iframe>Evidence-backed analysis snapshot. Validation record · Install · Homepage demo