Skip to main content
ArcSight

← HomepageAll repository proofValidation recordState of TS Architecture 2026

Repository proof

What ArcSight found in KafkaJS

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

Project: KafkaJS · Score: 92.8/100 (Excellent architecture) · 383 modules · 897 edges

arc impact src/utils/long
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/protocol/encoder75 dependents
  • src/protocol/decoder75 dependents
  • src/protocol/requests/apiKeys65 dependents
  • src/protocol/error49 dependents
  • src/errors41 dependents
  • src/utils/long14 dependents
  • src/protocol/message/compression9 dependents
  • src/utils/websiteUrl3 dependents
Blast radius, downstream modules
  • src/utils/long309 modules
  • src/errors205 modules
  • src/protocol/encoder192 modules
  • src/protocol/decoder167 modules
  • src/utils/websiteUrl159 modules
  • src/protocol/error156 modules
  • src/protocol/requests/apiKeys152 modules
  • src/protocol/message/compression39 modules
ModuleFan-inBlastRisk
src/utils/long14309CRITICAL
src/errors41205CRITICAL
src/protocol/encoder75192CRITICAL
src/protocol/decoder75167CRITICAL
src/utils/websiteUrl3159CRITICAL
src/protocol/error49156CRITICAL
src/protocol/requests/apiKeys65152CRITICAL
src/protocol/message/compression939HIGH

What ArcSight found

src/utils/long: fan-in 14, blast radius 309, CRITICAL. 383 modules and 897 dependency edges traced.

Why it matters

In KafkaJS, Change-risk signal at src/utils/long (fan-in 14) — merge impact can travel beyond the diff you see. Blast radius on src/utils/long reaches 309 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/utils/long
  • src/errors
  • src/protocol/encoder

What evidence supports it

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

    Architectural gravity centers

    • src/utils/long— concentrates too many responsibilities
    • src/utils/long— shared utility hub
    • src/errors— concentrates too many responsibilities
    • src/errors— shared utility hub
    • src/protocol/encoder— 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…) →

    KafkaJS architecture metrics
    Score
    92.8
    Modules
    383
    Edges
    897

    Metrics

    MetricValue
    Architecture score92.8/100
    Modules383
    Edges897

    FAQ

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

    Key takeaways

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

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