Skip to main content
ArcSight

← HomepageAll repository proofValidation recordState of TS Architecture 2026

Repository proof

What ArcSight found in Keystone

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

Project: Keystone (packages/core) · Score: 77.5/100 (Healthy architecture) · 179 modules · 536 edges

arc impact src/lib/core/utils
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/types93 dependents
  • src21 dependents
  • src/lib/core/initialise-lists20 dependents
  • src/lib/core/utils18 dependents
  • src/types/utils13 dependents
  • src/lib/core/graphql-errors11 dependents
  • src/lib/utils4 dependents
Blast radius, downstream modules
  • src/lib/core/utils144 modules
  • src/lib/core/graphql-errors144 modules
  • src/lib/utils144 modules
  • src/types143 modules
  • src143 modules
  • src/lib/core/initialise-lists143 modules
ModuleFan-inBlastRisk
src/lib/core/utils18144CRITICAL
src/lib/core/graphql-errors11144CRITICAL
src/lib/utils4144HIGH
src/types93143CRITICAL
src21143CRITICAL
src/lib/core/initialise-lists20143CRITICAL
src/types/utils13CRITICAL

What ArcSight found

src/lib/core/utils: fan-in 18, blast radius 144, CRITICAL. 179 modules and 536 dependency edges traced.

Why it matters

In Keystone (packages/core), Change-risk signal at src/lib/core/utils (fan-in 18) — merge impact can travel beyond the diff you see. Blast radius on src/lib/core/utils reaches 144 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/core/utils
  • src/lib/core/graphql-errors
  • src/lib/utils

What evidence supports it

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

  • Dependency cycles: 41
  • Layer violations: 13
  • Duplicate authorities: 10

Architectural gravity centers

  • src/lib/core/utils— concentrates too many responsibilities
  • src/lib/core/utils— shared utility hub
  • src/lib/core/utils— crosses a layer boundary
  • src/lib/core/graphql-errors— concentrates too many responsibilities
  • src/lib/core/graphql-errors— shared utility hub

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…) →

Keystone (packages/core) architecture metrics
Score
77.5
Modules
179
Edges
536

Metrics

MetricValue
Architecture score77.5/100
Modules179
Edges536
Dependency cycles41

FAQ

What did ArcSight find in Keystone (packages/core)?
src/lib/core/utils: fan-in 18, blast radius 144, CRITICAL. 179 modules and 536 dependency edges traced.
Why does the Keystone (packages/core) structure matter?
In Keystone (packages/core), Change-risk signal at src/lib/core/utils (fan-in 18) — merge impact can travel beyond the diff you see. Blast radius on src/lib/core/utils reaches 144 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 Keystone (packages/core)?
Start with src/lib/core/utils. 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/keystone/" width="320" height="180" frameborder="0"></iframe>

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