Skip to main content
ArcSight

← HomepageAll repository proofValidation recordState of TS Architecture 2026

Repository proof

What ArcSight found in ElectricSQL

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

Project: ElectricSQL (packages/typescript-client) · Score: 99.1/100 (Excellent architecture) · 16 modules · 38 edges

arc impact src/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/types9 dependents
  • src/error5 dependents
  • src/constants4 dependents
  • src/helpers4 dependents
  • src/column-mapper3 dependents
Blast radius, downstream modules
  • src/types9 modules
ModuleFan-inBlastRisk
src/types99LOW
src/error5LOW
src/constants4LOW
src/helpers4LOW
src/column-mapper3LOW

What ArcSight found

src/types: fan-in 9, blast radius 9, LOW. 16 modules and 38 dependency edges traced.

Why it matters

In ElectricSQL (packages/typescript-client), Change-risk signal at src/types (fan-in 9) — merge impact can travel beyond the diff you see. Blast radius on src/types reaches 9 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/types
  • src/error
  • src/constants

What evidence supports it

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

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

    ElectricSQL (packages/typescript-client) architecture metrics
    Score
    99.1
    Modules
    16
    Edges
    38

    Metrics

    MetricValue
    Architecture score99.1/100
    Modules16
    Edges38

    FAQ

    What did ArcSight find in ElectricSQL (packages/typescript-client)?
    src/types: fan-in 9, blast radius 9, LOW. 16 modules and 38 dependency edges traced.
    Why does the ElectricSQL (packages/typescript-client) structure matter?
    In ElectricSQL (packages/typescript-client), Change-risk signal at src/types (fan-in 9) — merge impact can travel beyond the diff you see. Blast radius on src/types reaches 9 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 ElectricSQL (packages/typescript-client)?
    Start with src/types. Run arc impact on that file before the change merges.

    Key takeaways

    • •Architecture score 99.1/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/electricsql/" width="320" height="180" frameborder="0"></iframe>

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