Skip to main content
ArcSight

← HomepageAll repository proofValidation recordState of TS Architecture 2026

Repository proof

What ArcSight found in n8n

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

Project: n8n (packages/workflow) · Score: 81.6/100 (Healthy architecture) · 112 modules · 311 edges

arc impact src/extensions/extensions
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/interfaces46 dependents
  • src/utils19 dependents
  • src/extensions/extensions14 dependents
  • src/errors/expression.error13 dependents
  • src/constants10 dependents
  • src/run-execution-data/run-execution-data6 dependents
  • src/expressions/expression-helpers5 dependents
Blast radius, downstream modules
  • src/extensions/extensions85 modules
  • src/constants78 modules
  • src/run-execution-data/run-execution-data78 modules
  • src/expressions/expression-helpers78 modules
  • src/interfaces77 modules
  • src/utils77 modules
  • src/errors/expression.error77 modules
ModuleFan-inBlastRisk
src/extensions/extensions1485HIGH
src/constants1078HIGH
src/run-execution-data/run-execution-data678CRITICAL
src/expressions/expression-helpers578CRITICAL
src/interfaces4677HIGH
src/utils1977HIGH
src/errors/expression.error1377HIGH

What ArcSight found

src/extensions/extensions: fan-in 14, blast radius 85, HIGH. 112 modules and 311 dependency edges traced.

Why it matters

In n8n (packages/workflow), Change-risk signal at src/extensions/extensions (fan-in 14) — merge impact can travel beyond the diff you see. Blast radius on src/extensions/extensions reaches 85 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/extensions/extensions
  • src/constants
  • src/run-execution-data/run-execution-data

What evidence supports it

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

  • Dependency cycles: 26
  • Duplicate authorities: 19

Architectural gravity centers

  • src/extensions/extensions— concentrates too many responsibilities
  • src/extensions/extensions— shared utility hub
  • src/constants— concentrates too many responsibilities
  • src/constants— shared utility hub
  • src/run-execution-data/run-execution-data— 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…) →

n8n (packages/workflow) architecture metrics
Score
81.6
Modules
112
Edges
311

Metrics

MetricValue
Architecture score81.6/100
Modules112
Edges311
Dependency cycles26

FAQ

What did ArcSight find in n8n (packages/workflow)?
src/extensions/extensions: fan-in 14, blast radius 85, HIGH. 112 modules and 311 dependency edges traced.
Why does the n8n (packages/workflow) structure matter?
In n8n (packages/workflow), Change-risk signal at src/extensions/extensions (fan-in 14) — merge impact can travel beyond the diff you see. Blast radius on src/extensions/extensions reaches 85 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 n8n (packages/workflow)?
Start with src/extensions/extensions. Run arc impact on that file before the change merges.

Key takeaways

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

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