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?

Run the same analysis on your repository in under 3 minutes.

Project: Cal.com (apps/web)Score: 97/100 (Excellent architecture)398 modules72 edges

arc impact components/booking/hooks/useBookingConfirmation

Install ArcSightRun arc impact in under 3 minutes Why trust ArcSight →

Proof summary

Four questions every public repository page must answer — see validation record · Hidden Dependencies problem.

What ArcSight found

High-risk module components/booking/hooks/useBookingConfirmation (fan-in 3) — LOW. components/booking/actions/bookingActions: fan-in 2, blast radius 2 modules. 398 modules and 72 dependency edges traced.

Why it matters

In Cal.com (apps/web), Change-risk signal at components/booking/hooks/useBookingConfirmation (fan-in 3) — 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/hooks/useBookingConfirmation
components/booking/types
components/security/TwoFactorAuthAPI

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

Architecture visualization

Diagrams are generated from ArcSight analysis data. Dependency graph and risk map show key modules; subsystem view shows high-level structure.

Dependency graph for this codebase — Dependency graph

Subsystem architecture for this codebase — Subsystem architecture

Architecture score & metrics

Score: 97/100 · Stability: 76/100 · Status: healthy · Confidence: 100%

Duplicate authorities: 23

Critical findings

components/booking/hooks/useBookingConfirmationLOWfan-in: 3
components/booking/typesLOWfan-in: 3
components/security/TwoFactorAuthAPILOWfan-in: 2
components/security/TwoFactorModalHeaderLOWfan-in: 2
components/booking/actions/storeLOWfan-in: 1

Hotspots

components/booking/actions/bookingActionsHIGHfan-in: 2blast: 2
components/booking/actions/BookingActionsStoreProviderHIGHfan-in: 2blast: 2
app/_trpc/trpc-clientHIGHfan-in: 1blast: 1
app/(use-page-wrapper)/settings/(settings-layout)/layoutHIGHfan-in: 1blast: 1
app/providersHIGHfan-in: 1blast: 1
components/apps/AppPageHIGHfan-in: 1blast: 1
components/booking/AcceptBookingButtonHIGHfan-in: 1blast: 1
components/booking/actions/BookingActionsDropdownHIGHfan-in: 1blast: 1
components/booking/RejectBookingButtonHIGHfan-in: 1blast: 1
components/phone-input/PhoneInputHIGHfan-in: 1blast: 1

CLI workflow

Scan → Fix → Finish → Watch. Nothing else required.

arc scanFind issues
arc fixApply fixes
arc finishResolve remaining
arc watchKeep clean (Pro)

More commands (explain, impact, guard…) →

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.

npm install -g arcsight

arc impact <path>

Install →

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

Hidden Dependencies problem

Evidence-backed analysis snapshot. Validation record · Install · Homepage demo