What ArcSight found
components/booking/actions/bookingActions: fan-in 2, blast radius 2, HIGH. 398 modules and 72 dependency edges traced.
← HomepageAll repository proofValidation recordState of TS Architecture 2026
Repository proof
What ArcSight found in Cal.com
Real arc impact on Cal.com (apps/web) — blast radius, break paths, and evidence. Same question as the homepage: what breaks if I change this?
Project: Cal.com (apps/web) · Score: 97/100 (Excellent architecture) · 398 modules · 72 edges
arc impact components/booking/actions/bookingActionsRun the same analysis on your repository in under 3 minutes.
Proof summary
Four questions every public repository page must answer — see validation record.
Hidden dependencies in Cal.com
Modules to inspect
One row per module. Fan-in is direct dependents. Blast radius is downstream modules reachable from that file.
- components/booking/hooks/useBookingConfirmation3 dependents
- components/booking/types3 dependents
- components/booking/actions/bookingActions2 dependents
- components/booking/actions/BookingActionsStoreProvider2 dependents
- components/security/TwoFactorAuthAPI2 dependents
- components/security/TwoFactorModalHeader2 dependents
- app/_trpc/trpc-client1 dependents
- app/(use-page-wrapper)/settings/(settings-layout)/layout1 dependents
- components/booking/actions/bookingActions2 modules
- components/booking/actions/BookingActionsStoreProvider2 modules
- app/_trpc/trpc-client1 modules
- app/(use-page-wrapper)/settings/(settings-layout)/layout1 modules
- app/providers1 modules
- components/apps/AppPage1 modules
- components/booking/AcceptBookingButton1 modules
- components/booking/actions/BookingActionsDropdown1 modules
| Module | Fan-in | Blast | Risk |
|---|---|---|---|
| components/booking/actions/bookingActions | 2 | 2 | HIGH |
| components/booking/actions/BookingActionsStoreProvider | 2 | 2 | HIGH |
| app/_trpc/trpc-client | 1 | 1 | HIGH |
| app/(use-page-wrapper)/settings/(settings-layout)/layout | 1 | 1 | HIGH |
| app/providers | 1 | 1 | HIGH |
| components/apps/AppPage | 1 | 1 | HIGH |
| components/booking/AcceptBookingButton | 1 | 1 | HIGH |
| components/booking/actions/BookingActionsDropdown | 1 | 1 | HIGH |
| components/booking/RejectBookingButton | 1 | 1 | HIGH |
| components/phone-input/PhoneInput | 1 | 1 | HIGH |
| components/security/DisableTwoFactorModal | 1 | 1 | HIGH |
| components/security/EnableTwoFactorModal | 1 | 1 | HIGH |
| components/booking/hooks/useBookingConfirmation | 3 | LOW | |
| components/booking/types | 3 | LOW | |
| components/security/TwoFactorAuthAPI | 2 | LOW | |
| components/security/TwoFactorModalHeader | 2 | LOW | |
| components/booking/actions/store | 1 | LOW |
Why it matters
In Cal.com (apps/web), Change-risk signal at components/booking/actions/bookingActions (fan-in 2) — merge impact can travel beyond the diff you see. Blast radius on components/booking/actions/bookingActions reaches 2 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
- components/booking/actions/bookingActions
- components/booking/actions/BookingActionsStoreProvider
- app/_trpc/trpc-client
What evidence supports it
- Local CLI analysis — repository source stays on your machine
- Structural coverage: 398 modules, 72 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: 97/100 · Stability: 76/100 · Status: healthy · Confidence: 100%
- Duplicate authorities: 23
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
- 97
- Modules
- 398
- Edges
- 72
Metrics
| Metric | Value |
|---|---|
| Architecture score | 97/100 |
| Modules | 398 |
| Edges | 72 |
FAQ
- What did ArcSight find in Cal.com (apps/web)?
- components/booking/actions/bookingActions: fan-in 2, blast radius 2, HIGH. 398 modules and 72 dependency edges traced.
- Why does the Cal.com (apps/web) structure matter?
- In Cal.com (apps/web), Change-risk signal at components/booking/actions/bookingActions (fan-in 2) — merge impact can travel beyond the diff you see. Blast radius on components/booking/actions/bookingActions reaches 2 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 Cal.com (apps/web)?
- Start with components/booking/actions/bookingActions. Run arc impact on that file before the change merges.
Key takeaways
- •Architecture score 97/100 indicates a healthy structure with room to reduce cycles and violations.
- •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/calcom/" width="320" height="180" frameborder="0"></iframe>Explore
Evidence-backed analysis snapshot. Validation record · Install · Homepage demo