Skip to main content
ArcSight

← HomepageAll repository proofValidation recordState of TS Architecture 2026

Repository proof

What ArcSight found in Convex

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

Project: Convex · Score: 59.6/100 (Moderate technical debt) · 245 modules · 1,155 edges

arc impact src/values/value
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/values44 dependents
  • src/values/value23 dependents
  • src/server/api18 dependents
  • src/server/data_model17 dependents
  • src/common12 dependents
  • src/values/validator7 dependents
  • src/values/validators6 dependents
  • src/server/system_fields5 dependents
Blast radius, downstream modules
  • src/values/value186 modules
  • src/common186 modules
  • src/values178 modules
  • src/values/validator178 modules
  • src/values/validators178 modules
  • src/server/data_model158 modules
  • src/server/system_fields158 modules
  • src/server/api143 modules
ModuleFan-inBlastRisk
src/values/value23186CRITICAL
src/common12186CRITICAL
src/values44178CRITICAL
src/values/validator7178CRITICAL
src/values/validators6178CRITICAL
src/server/data_model17158CRITICAL
src/server/system_fields5158HIGH
src/server/api18143CRITICAL
src/values/errors5CRITICAL
src/values/base642CRITICAL

What ArcSight found

src/values/value: fan-in 23, blast radius 186, CRITICAL. 245 modules and 1,155 dependency edges traced.

Why it matters

In Convex, Change-risk signal at src/values/value (fan-in 23) — merge impact can travel beyond the diff you see. Blast radius on src/values/value reaches 186 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/values/value
  • src/common
  • src/values

What evidence supports it

  • Local CLI analysis — repository source stays on your machine
  • Structural coverage: 245 modules, 1,155 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: 59.6/100 · Stability: 3/100 · Status: critical · Confidence: 100%

  • Dependency cycles: 100+
  • Duplicate authorities: 81

Architectural gravity centers

  • src/values/value— concentrates too many responsibilities
  • src/values/value— shared utility hub
  • src/values/value— sits on a dependency cycle
  • src/common— sits on a dependency cycle
  • src/values— 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…) →

Convex architecture metrics
Score
59.6
Modules
245
Edges
1,155

Metrics

MetricValue
Architecture score59.6/100
Modules245
Edges1,155
Dependency cycles100+

FAQ

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

Key takeaways

  • •Structural scan reports dependency cycles — inspect impact paths before refactors that cross module boundaries.
  • •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/convex/" width="320" height="180" frameborder="0"></iframe>

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