Skip to main content
ArcSight

← HomepageAll repository proofValidation recordState of TS Architecture 2026

Repository proof

What ArcSight found in Clerk

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

Project: Clerk (packages/backend) · Score: 83.8/100 (Healthy architecture) · 137 modules · 464 edges

arc impact src/api/resources/Enums
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/api/resources/JSON58 dependents
  • src/api/endpoints/AbstractApi33 dependents
  • src/util/path29 dependents
  • src/api/resources/Deserializer19 dependents
  • src/api/resources/Enums15 dependents
  • src/api/resources13 dependents
  • src/constants9 dependents
  • src/runtime8 dependents
Blast radius, downstream modules
  • src/api/resources/Enums108 modules
  • src/api/resources/JSON107 modules
  • src/runtime56 modules
  • src/constants54 modules
  • src/util/path52 modules
  • src/api/resources/Deserializer51 modules
  • src/api/endpoints/AbstractApi49 modules
  • src/api/resources/Verification37 modules
ModuleFan-inBlastRisk
src/api/resources/Enums15108CRITICAL
src/api/resources/JSON58107CRITICAL
src/runtime856CRITICAL
src/constants954CRITICAL
src/util/path2952HIGH
src/api/resources/Deserializer1951MEDIUM
src/api/endpoints/AbstractApi3349HIGH
src/api/resources/Verification737CRITICAL
src/api/resources1329CRITICAL

What ArcSight found

src/api/resources/Enums: fan-in 15, blast radius 108, CRITICAL. 137 modules and 464 dependency edges traced.

Why it matters

In Clerk (packages/backend), Change-risk signal at src/api/resources/Enums (fan-in 15) — merge impact can travel beyond the diff you see. Blast radius on src/api/resources/Enums reaches 108 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/api/resources/Enums
  • src/api/resources/JSON
  • src/runtime

What evidence supports it

  • Local CLI analysis — repository source stays on your machine
  • Structural coverage: 137 modules, 464 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: 83.8/100 · Stability: 10/100 · Status: healthy · Confidence: 100%

  • Dependency cycles: 24
  • Duplicate authorities: 7

Architectural gravity centers

  • src/api/resources/Enums— concentrates too many responsibilities
  • src/api/resources/Enums— shared utility hub
  • src/api/resources/JSON— concentrates too many responsibilities
  • src/api/resources/JSON— shared utility hub
  • src/runtime— 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…) →

Clerk (packages/backend) architecture metrics
Score
83.8
Modules
137
Edges
464

Metrics

MetricValue
Architecture score83.8/100
Modules137
Edges464
Dependency cycles24

FAQ

What did ArcSight find in Clerk (packages/backend)?
src/api/resources/Enums: fan-in 15, blast radius 108, CRITICAL. 137 modules and 464 dependency edges traced.
Why does the Clerk (packages/backend) structure matter?
In Clerk (packages/backend), Change-risk signal at src/api/resources/Enums (fan-in 15) — merge impact can travel beyond the diff you see. Blast radius on src/api/resources/Enums reaches 108 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 Clerk (packages/backend)?
Start with src/api/resources/Enums. Run arc impact on that file before the change merges.

Key takeaways

  • •Architecture score 83.8/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.

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/clerk/" width="320" height="180" frameborder="0"></iframe>

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