Skip to main content
ArcSight

← HomepageAll repository proofValidation recordState of TS Architecture 2026

Repository proof

What ArcSight found in Refine

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

Project: Refine (packages/core) · Score: 74.4/100 (Moderate technical debt) · 198 modules · 664 edges

arc impact src/contexts/data/types
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/contexts/data/types61 dependents
  • src/hooks43 dependents
  • src/contexts/notification/types27 dependents
  • src/contexts/resource/types26 dependents
  • src/contexts/router/types20 dependents
  • src/contexts/live/types16 dependents
  • src/definitions/types14 dependents
  • src/contexts/auth/types12 dependents
Blast radius, downstream modules
  • src/contexts/data/types148 modules
  • src/contexts/resource/types129 modules
  • src/contexts/router/types119 modules
  • src/contexts/i18n108 modules
  • src/contexts/router108 modules
  • src/contexts/live/types106 modules
  • src/definitions/types106 modules
  • src/contexts/notification/types105 modules
ModuleFan-inBlastRisk
src/contexts/data/types61148CRITICAL
src/contexts/resource/types26129CRITICAL
src/contexts/router/types20119CRITICAL
src/contexts/i18n7108CRITICAL
src/contexts/router7108CRITICAL
src/contexts/live/types16106CRITICAL
src/definitions/types14106CRITICAL
src/contexts/notification/types27105CRITICAL
src/contexts/auth/types12105CRITICAL
src/hooks43CRITICAL
src/contexts/auditLog/types5CRITICAL

What ArcSight found

src/contexts/data/types: fan-in 61, blast radius 148, CRITICAL. 198 modules and 664 dependency edges traced.

Why it matters

In Refine (packages/core), Change-risk signal at src/contexts/data/types (fan-in 61) — merge impact can travel beyond the diff you see. Blast radius on src/contexts/data/types reaches 148 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/contexts/data/types
  • src/contexts/resource/types
  • src/contexts/router/types

What evidence supports it

  • Local CLI analysis — repository source stays on your machine
  • Structural coverage: 198 modules, 664 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: 74.4/100 · Stability: 6/100 · Status: moderate_risk · Confidence: 100%

  • Dependency cycles: 73
  • Duplicate authorities: 5

Architectural gravity centers

  • src/contexts/data/types— concentrates too many responsibilities
  • src/contexts/data/types— shared utility hub
  • src/contexts/resource/types— concentrates too many responsibilities
  • src/contexts/resource/types— shared utility hub
  • src/contexts/router/types— 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…) →

Refine (packages/core) architecture metrics
Score
74.4
Modules
198
Edges
664

Metrics

MetricValue
Architecture score74.4/100
Modules198
Edges664
Dependency cycles73

FAQ

What did ArcSight find in Refine (packages/core)?
src/contexts/data/types: fan-in 61, blast radius 148, CRITICAL. 198 modules and 664 dependency edges traced.
Why does the Refine (packages/core) structure matter?
In Refine (packages/core), Change-risk signal at src/contexts/data/types (fan-in 61) — merge impact can travel beyond the diff you see. Blast radius on src/contexts/data/types reaches 148 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 Refine (packages/core)?
Start with src/contexts/data/types. Run arc impact on that file before the change merges.

Key takeaways

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

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