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/core
Install ArcSight →Why trust ArcSight →

Run the same analysis on your repository in under 3 minutes.

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

    Try it in the terminal

    Simulated arc analyze output from the dataset. No analysis runs in the browser.

    ArcSight CLI (simulated)
    $ arc scan nats
    Architecture Score: 96.3
    Modules: 31
    Cycles: 0
    Hotspots: 7

    Simulated from dataset. No analysis is run in the browser.

    Similar architectures

    Repositories with the same language and category, ordered by similar complexity and size.

    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)?
    NATS.js (core) has 31 modules and an architecture score of 96.3/100.
    Why does the NATS.js (core) structure matter?
    The NATS.js (core) score is 96.3/100 across 31 modules and 114 edges.
    Which file should I inspect first in NATS.js (core)?
    Start with src/core. 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>

    Explore

    LanguageCategoryModular MonolithHigh CouplingCompareLeaderboard

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