Skip to main content
ArcSight

← HomepageAll repository proofValidation recordState of TS Architecture 2026

Repository proof

What ArcSight found in Next.js

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

Project: Next.js (packages/next) · Score: 89/100 (A) · 1,942 modules · 4,489 edges

arc impact src/server/config-shared
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.

Blast radius in Next.js

Definitions: Change Impact definition · High Fan-In definition

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/server/config-shared46 dependents
  • src/shared/lib/app-router-types45 dependents
  • src/shared/lib/segment23 dependents
  • src/types21 dependents
  • src/server/lib/lru-cache12 dependents
Blast radius, downstream modules
  • src/server/config-shared423 modules
  • src/types423 modules
ModuleFan-inBlastRiskSubsystem
src/server/config-shared46423CRITICALnext-next-devtools
src/types21423CRITICALnext-next-devtools
src/shared/lib/app-router-types45CRITICAL
src/shared/lib/segment23HIGH
src/server/lib/lru-cache12HIGH

What ArcSight found

src/server/config-shared: fan-in 46, blast radius 423, CRITICAL. 1,942 modules and 4,489 dependency edges traced.

Why it matters

In Next.js (packages/next), Change-risk signal at src/server/config-shared (fan-in 46) — merge impact can travel beyond the diff you see. Blast radius on src/server/config-shared reaches 423 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/server/config-shared
  • src/types
  • src/shared/lib/app-router-types

What evidence supports it

  • Local CLI analysis — repository source stays on your machine
  • Structural coverage: 1,942 modules, 4,489 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: 89/100

    Dependency corridors

    Repeated paths where changes propagate through the same modules.

    • src/server/config-shared → src/server/request-meta → src/server/request/params
    • src/types → src/shared/lib/utils → src/server/app-render

    Subsystem overview

    • next-next-devtools (120 modules)
    • client-app-call-server (85 modules)

    Architectural gravity centers

    • src/types— shared utility hub
    • src/server/config-shared— central orchestrator

    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…) →

    Next.js (packages/next) architecture metrics
    Score
    89
    Modules
    1,942
    Edges
    4,489

    Metrics

    MetricValue
    Architecture score89/100
    Modules1,942
    Edges4,489

    FAQ

    What did ArcSight find in Next.js (packages/next)?
    src/server/config-shared: fan-in 46, blast radius 423, CRITICAL. 1,942 modules and 4,489 dependency edges traced.
    Why does the Next.js (packages/next) structure matter?
    In Next.js (packages/next), Change-risk signal at src/server/config-shared (fan-in 46) — merge impact can travel beyond the diff you see. Blast radius on src/server/config-shared reaches 423 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 Next.js (packages/next)?
    Start with src/server/config-shared. Run arc impact on that file before the change merges.

    Key takeaways

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

    Explore

    Blast radius in Next.jsChange Impact definitionHigh Fan-In definition

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