Skip to main content
ArcSight

← HomepageAll repository proofValidation recordState of TS Architecture 2026

Repository proof

What ArcSight found in NATS.js

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

Project: NATS.js (core) · Score: 96.3/100 (Excellent architecture) · 31 modules · 114 edges

arc impact src/encoders
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/core18 dependents
  • src/encoders12 dependents
  • src/errors12 dependents
  • src/util10 dependents
  • src/nuid3 dependents
Blast radius, downstream modules
  • src/encoders20 modules
  • src/errors20 modules
  • src/core19 modules
  • src/util11 modules
ModuleFan-inBlastRisk
src/encoders1220LOW
src/errors1220LOW
src/core1819LOW
src/util1011LOW
src/nuid3LOW

What ArcSight found

src/encoders: fan-in 12, blast radius 20, LOW. 31 modules and 114 dependency edges traced.

Why it matters

In NATS.js (core), Change-risk signal at src/encoders (fan-in 12) — merge impact can travel beyond the diff you see. Blast radius on src/encoders reaches 20 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/encoders
  • src/errors
  • src/core

What evidence supports it

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

    Architectural gravity centers

    • src/encoders— concentrates too many responsibilities
    • src/encoders— shared utility hub
    • src/errors— concentrates too many responsibilities
    • src/errors— shared utility hub
    • src/core— 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…) →

    NATS.js (core) architecture metrics
    Score
    96.3
    Modules
    31
    Edges
    114

    Metrics

    MetricValue
    Architecture score96.3/100
    Modules31
    Edges114

    FAQ

    What did ArcSight find in NATS.js (core)?
    src/encoders: fan-in 12, blast radius 20, LOW. 31 modules and 114 dependency edges traced.
    Why does the NATS.js (core) structure matter?
    In NATS.js (core), Change-risk signal at src/encoders (fan-in 12) — merge impact can travel beyond the diff you see. Blast radius on src/encoders reaches 20 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 NATS.js (core)?
    Start with src/encoders. Run arc impact on that file before the change merges.

    Key takeaways

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

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