Skip to main content
ArcSight

← HomepageAll repository proofValidation recordState of TS Architecture 2026

Repository proof

What ArcSight found in Supabase

Real arc impact on Supabase (packages/ui) — blast radius, break paths, and evidence. Same question as the homepage: what breaks if I change this?

Project: Supabase (packages/ui) · Score: 93.9/100 (Excellent architecture) · 159 modules · 185 edges

arc impact src/lib/utils/cn
Install ArcSight →Why trust ArcSight →

Run 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.

Fan-in, direct dependents
  • src/lib/utils/cn54 dependents
  • src/components/Icon/IconBase20 dependents
  • src/lib/theme/styleHandler8 dependents
  • src/lib/theme/defaultTheme4 dependents
  • src/components/ThemeProvider/ThemeProvider1 dependents
  • src/lib/commonCva1 dependents
  • src/components/Icon/IconContext1 dependents
  • src/lib/utils/clipboard1 dependents
Blast radius, downstream modules
  • src/lib/utils/cn118 modules
  • src/lib/theme/defaultTheme58 modules
  • src/components/ThemeProvider/ThemeProvider54 modules
  • src/lib/theme/styleHandler53 modules
  • src/lib/commonCva42 modules
  • src/components/Icon/IconContext41 modules
  • src/components/Icon/IconBase40 modules
  • src/lib/utils/clipboard18 modules
ModuleFan-inBlastRisk
src/lib/utils/cn54118CRITICAL
src/lib/theme/defaultTheme458MEDIUM
src/components/ThemeProvider/ThemeProvider154MEDIUM
src/lib/theme/styleHandler853MEDIUM
src/lib/commonCva142CRITICAL
src/components/Icon/IconContext141CRITICAL
src/components/Icon/IconBase2040MEDIUM
src/lib/utils/clipboard118HIGH
src/lib/utils/mergeDeep118HIGH
src/lib/utils/randomIdGenerator118HIGH

What ArcSight found

src/lib/utils/cn: fan-in 54, blast radius 118, CRITICAL. 159 modules and 185 dependency edges traced.

Why it matters

In Supabase (packages/ui), Change-risk signal at src/lib/utils/cn (fan-in 54) — merge impact can travel beyond the diff you see. Blast radius on src/lib/utils/cn reaches 118 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/lib/utils/cn
  • src/lib/theme/defaultTheme
  • src/components/ThemeProvider/ThemeProvider

What evidence supports it

  • Local CLI analysis — repository source stays on your machine
  • Structural coverage: 159 modules, 185 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.

Dependency graph
Dependency graph for this codebase
Subsystem architecture
Subsystem architecture for this codebase
Risk map
Risk map for this codebase

Architecture score & metrics

Score: 93.9/100 · Stability: 44/100 · Status: healthy · Confidence: 100%

  • Duplicate authorities: 3

Architectural gravity centers

  • src/lib/utils/cn— concentrates too many responsibilities
  • src/lib/utils/cn— shared utility hub
  • src/lib/theme/defaultTheme— concentrates too many responsibilities
  • src/components/ThemeProvider/ThemeProvider— concentrates too many responsibilities
  • src/lib/theme/styleHandler— concentrates too many responsibilities

CLI workflow

Impact, then scan, fix, finish, and watch.

  • arc impact <file>See what a change breaks
  • arc scanFind issues
  • arc fixApply fixes
  • arc finishResolve remaining
  • arc watchKeep clean

More commands (explain, guard…) →

Supabase (packages/ui) architecture metrics
Score
93.9
Modules
159
Edges
185

Metrics

MetricValue
Architecture score93.9/100
Modules159
Edges185

FAQ

What did ArcSight find in Supabase (packages/ui)?
src/lib/utils/cn: fan-in 54, blast radius 118, CRITICAL. 159 modules and 185 dependency edges traced.
Why does the Supabase (packages/ui) structure matter?
In Supabase (packages/ui), Change-risk signal at src/lib/utils/cn (fan-in 54) — merge impact can travel beyond the diff you see. Blast radius on src/lib/utils/cn reaches 118 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 Supabase (packages/ui)?
Start with src/lib/utils/cn. Run arc impact on that file before the change merges.

Key takeaways

  • •Architecture score 93.9/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 ArcSight →

Embed this report

Use this iframe to show the architecture badge on your site.

<iframe src="https://arcsight.ai/embed/supabase/" width="320" height="180" frameborder="0"></iframe>

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