Skip to main content
ArcSight

← HomepageAll repository proofValidation recordState of TS Architecture 2026

Repository proof

What ArcSight found in ArcSight

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

Project: ArcSight · Score: 91.5/100 (Excellent architecture) · 978 modules · 2,633 edges

arc impact src/graph/core/graphTypes
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/graph/core/graphTypes74 dependents
  • src/deps/graphBuild53 dependents
  • src/deps/graphCache51 dependents
  • src/invariants/types27 dependents
  • src/deps/graphQueries24 dependents
  • src/invariants/runInvariants24 dependents
  • src/core/discovery/types14 dependents
  • src/core/discovery/ignoreRules10 dependents
Blast radius, downstream modules
  • src/graph/core/graphTypes191 modules
  • src/core/discovery/types172 modules
  • src/core/discovery/ignoreRules150 modules
  • src/invariants/types149 modules
  • src/graph/analysis/layers/types149 modules
  • src/deps/graphCache145 modules
  • src/deps/graphQueries143 modules
  • src/graph/analysis/rules/types143 modules
ModuleFan-inBlastRisk
src/graph/core/graphTypes74191CRITICAL
src/core/discovery/types14172CRITICAL
src/core/discovery/ignoreRules10150CRITICAL
src/invariants/types27149CRITICAL
src/graph/analysis/layers/types8149CRITICAL
src/deps/graphCache51145CRITICAL
src/deps/graphQueries24143CRITICAL
src/graph/analysis/rules/types10143CRITICAL
src/invariants/runInvariants24134CRITICAL
src/deps/graphBuild53CRITICAL

What ArcSight found

src/graph/core/graphTypes: fan-in 74, blast radius 191, CRITICAL. 978 modules and 2,633 dependency edges traced.

Why it matters

In ArcSight, Change-risk signal at src/graph/core/graphTypes (fan-in 74) — merge impact can travel beyond the diff you see. Blast radius on src/graph/core/graphTypes reaches 191 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/graph/core/graphTypes
  • src/core/discovery/types
  • src/core/discovery/ignoreRules

What evidence supports it

  • Local CLI analysis — repository source stays on your machine
  • Structural coverage: 978 modules, 2,633 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: 91.5/100 · Stability: 34/100 · Status: healthy · Confidence: 100%

    Architectural gravity centers

    • src/graph/core/graphTypes— concentrates too many responsibilities
    • src/graph/core/graphTypes— shared utility hub
    • src/core/discovery/types— concentrates too many responsibilities
    • src/core/discovery/types— shared utility hub
    • src/core/discovery/ignoreRules— 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…) →

    ArcSight architecture metrics
    Score
    91.5
    Modules
    978
    Edges
    2,633

    Metrics

    MetricValue
    Architecture score91.5/100
    Modules978
    Edges2,633

    FAQ

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

    Key takeaways

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

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