Skip to main content
ArcSight

← HomepageAll repository proofValidation recordState of TS Architecture 2026

Repository proof

What ArcSight found in Effect

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

Project: Effect (packages/effect) · Score: 44.3/100 (High architecture risk) · 363 modules · 3,365 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/Function186 dependents
  • src/Effect141 dependents
  • src/Option140 dependents
  • src/Predicate122 dependents
  • src/Pipeable116 dependents
  • src/Types114 dependents
  • src/Equal82 dependents
  • src/Hash42 dependents
Blast radius, downstream modules
  • src/Types322 modules
  • src/Function319 modules
  • src/Predicate308 modules
  • src/Hash295 modules
  • src/Pipeable294 modules
  • src/Equal294 modules
  • src/ExecutionStrategy293 modules
  • src/ChildExecutorDecision293 modules
ModuleFan-inBlastRisk
src/Types114322CRITICAL
src/Function186319CRITICAL
src/Predicate122308CRITICAL
src/Hash42295CRITICAL
src/Pipeable116294CRITICAL
src/Equal82294CRITICAL
src/ExecutionStrategy7293HIGH
src/ChildExecutorDecision6293HIGH
src/internal/executionStrategy5293HIGH
src/Effect141CRITICAL
src/Option140CRITICAL

What ArcSight found

src/Types: fan-in 114, blast radius 322, CRITICAL. 363 modules and 3,365 dependency edges traced.

Why it matters

In Effect (packages/effect), Change-risk signal at src/Types (fan-in 114) — merge impact can travel beyond the diff you see. Blast radius on src/Types reaches 322 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/Function
  • src/Predicate

What evidence supports it

  • Local CLI analysis — repository source stays on your machine
  • Structural coverage: 363 modules, 3,365 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: 44.3/100 · Stability: 1/100 · Status: critical · Confidence: 100%

  • Dependency cycles: 100+
  • Duplicate authorities: 311

Architectural gravity centers

  • src/Types— concentrates too many responsibilities
  • src/Types— shared utility hub
  • src/Function— concentrates too many responsibilities
  • src/Function— shared utility hub
  • src/Predicate— 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…) →

Effect (packages/effect) architecture metrics
Score
44.3
Modules
363
Edges
3,365

Metrics

MetricValue
Architecture score44.3/100
Modules363
Edges3,365
Dependency cycles100+

FAQ

What did ArcSight find in Effect (packages/effect)?
src/Types: fan-in 114, blast radius 322, CRITICAL. 363 modules and 3,365 dependency edges traced.
Why does the Effect (packages/effect) structure matter?
In Effect (packages/effect), Change-risk signal at src/Types (fan-in 114) — merge impact can travel beyond the diff you see. Blast radius on src/Types reaches 322 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 Effect (packages/effect)?
Start with src/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/effect/" width="320" height="180" frameborder="0"></iframe>

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