Skip to main content
ArcSight

← HomepageAll repository proofValidation recordState of TS Architecture 2026

Repository proof

What ArcSight found in Temporal TypeScript SDK

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

Project: Temporal TypeScript SDK (packages/workflow) · Score: 93/100 (Excellent architecture) · 26 modules · 81 edges

arc impact src/interfaces
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/global-attributes12 dependents
  • src/interfaces8 dependents
  • src/stack-helpers7 dependents
  • src/cancellation-scope6 dependents
  • src/interceptor-composition6 dependents
  • src/interceptors6 dependents
  • src/errors5 dependents
  • src/sinks4 dependents
Blast radius, downstream modules
  • src/interfaces18 modules
  • src/global-attributes16 modules
  • src/stack-helpers16 modules
  • src/cancellation-scope16 modules
  • src/interceptor-composition16 modules
  • src/interceptors16 modules
  • src/sinks16 modules
  • src/workflow16 modules
ModuleFan-inBlastRisk
src/interfaces818LOW
src/global-attributes1216LOW
src/stack-helpers716LOW
src/cancellation-scope616LOW
src/interceptor-composition616CRITICAL
src/interceptors616CRITICAL
src/sinks416CRITICAL
src/workflow416CRITICAL
src/internals316CRITICAL
src/logs216CRITICAL
src/nexus216CRITICAL
src/errors5LOW

What ArcSight found

src/interfaces: fan-in 8, blast radius 18, LOW. 26 modules and 81 dependency edges traced.

Why it matters

In Temporal TypeScript SDK (packages/workflow), Change-risk signal at src/interfaces (fan-in 8) — merge impact can travel beyond the diff you see. Blast radius on src/interfaces reaches 18 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/interfaces
  • src/global-attributes
  • src/stack-helpers

What evidence supports it

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

  • Dependency cycles: 10
  • Duplicate authorities: 1

Architectural gravity centers

  • src/global-attributes— concentrates too many responsibilities
  • src/global-attributes— sits on a dependency cycle
  • src/global-attributes— 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…) →

Temporal TypeScript SDK (packages/workflow) architecture metrics
Score
93
Modules
26
Edges
81

Metrics

MetricValue
Architecture score93/100
Modules26
Edges81
Dependency cycles10

FAQ

What did ArcSight find in Temporal TypeScript SDK (packages/workflow)?
src/interfaces: fan-in 8, blast radius 18, LOW. 26 modules and 81 dependency edges traced.
Why does the Temporal TypeScript SDK (packages/workflow) structure matter?
In Temporal TypeScript SDK (packages/workflow), Change-risk signal at src/interfaces (fan-in 8) — merge impact can travel beyond the diff you see. Blast radius on src/interfaces reaches 18 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 Temporal TypeScript SDK (packages/workflow)?
Start with src/interfaces. Run arc impact on that file before the change merges.

Key takeaways

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

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