Skip to main content
ArcSight

← HomepageAll repository proofValidation recordState of TS Architecture 2026

Repository proof

What ArcSight found in Backstage

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

Project: Backstage (packages/ui) · Score: 88.6/100 (Healthy architecture) · 301 modules · 916 edges

arc impact src/hooks/useDefinition
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: 88.6/100 · Stability: 22/100 · Status: healthy · Confidence: 100%

  • Dependency cycles: 3
  • Layer violations: 1
  • Duplicate authorities: 5

Architectural gravity centers

  • src/types— concentrates too many responsibilities
  • src/types— shared utility hub
  • src/utils/utilityClassMap— crosses a layer boundary
  • src/hooks/useDefinition/types— crosses a layer boundary
  • src/hooks/useDefinition— 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 backstage
Architecture Score: 88.6
Modules: 301
Cycles: 3
Hotspots: 15

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

Backstage (packages/ui) architecture metrics
Score
88.6
Modules
301
Edges
916

Metrics

MetricValue
Architecture score88.6/100
Modules301
Edges916
Dependency cycles3

FAQ

What did ArcSight find in Backstage (packages/ui)?
Backstage (packages/ui) has 301 modules and an architecture score of 88.6/100.
Why does the Backstage (packages/ui) structure matter?
The Backstage (packages/ui) score is 88.6/100 across 301 modules and 916 edges.
Which file should I inspect first in Backstage (packages/ui)?
Start with src/hooks/useDefinition. Run arc impact on that file before the change merges.

Key takeaways

  • •Architecture score 88.6/100 indicates a healthy structure with room to reduce cycles and violations.
  • •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/backstage/" width="320" height="180" frameborder="0"></iframe>

Explore

LanguageCategoryHigh CouplingModular MonolithDistributed ModulesCompareLeaderboard

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