What ArcSight found
src/types: fan-in 24, blast radius 252, CRITICAL. 301 modules and 916 dependency edges traced.
← 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/typesRun 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.
- src/hooks/useDefinition113 dependents
- src/components/Flex30 dependents
- src/components/Text26 dependents
- src/types24 dependents
- src/components/Box22 dependents
- src/provider17 dependents
- src/components/FieldLabel16 dependents
- src/components/FieldLabel/types14 dependents
- src/types252 modules
- src/utils/utilityClassMap232 modules
- src/hooks/useDefinition/types231 modules
- src/hooks/useDefinition226 modules
- src/components/FieldLabel/types111 modules
- src/components/Box97 modules
- src/components/FieldLabel85 modules
- src/components/FieldError85 modules
| Module | Fan-in | Blast | Risk |
|---|---|---|---|
| src/types | 24 | 252 | CRITICAL |
| src/utils/utilityClassMap | 2 | 232 | MEDIUM |
| src/hooks/useDefinition/types | 4 | 231 | MEDIUM |
| src/hooks/useDefinition | 113 | 226 | CRITICAL |
| src/components/FieldLabel/types | 14 | 111 | CRITICAL |
| src/components/Box | 22 | 97 | CRITICAL |
| src/components/FieldLabel | 16 | 85 | CRITICAL |
| src/components/FieldError | 11 | 85 | CRITICAL |
| src/components/Flex | 30 | 82 | CRITICAL |
| src/components/Text | 26 | 79 | CRITICAL |
| src/components/Link | 8 | 71 | CRITICAL |
| src/components/Button | 10 | 68 | CRITICAL |
| src/provider | 17 | 67 | CRITICAL |
| src/utils/linkUtils | 5 | CRITICAL | |
| src/analytics/types | 4 | CRITICAL | |
| src/analytics/useAnalytics | 3 | CRITICAL |
Why it matters
In Backstage (packages/ui), Change-risk signal at src/types (fan-in 24) — merge impact can travel beyond the diff you see. Blast radius on src/types reaches 252 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/types
- src/utils/utilityClassMap
- src/hooks/useDefinition/types
What evidence supports it
- Local CLI analysis — repository source stays on your machine
- Structural coverage: 301 modules, 916 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.
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 responsibilitiessrc/types— shared utility hubsrc/utils/utilityClassMap— crosses a layer boundarysrc/hooks/useDefinition/types— crosses a layer boundarysrc/hooks/useDefinition— concentrates too many responsibilities
CLI workflow
Impact, then scan, fix, finish, and watch.
arc impact <file>See what a change breaksarc scanFind issuesarc fixApply fixesarc finishResolve remainingarc watchKeep clean
- Score
- 88.6
- Modules
- 301
- Edges
- 916
Metrics
| Metric | Value |
|---|---|
| Architecture score | 88.6/100 |
| Modules | 301 |
| Edges | 916 |
| Dependency cycles | 3 |
FAQ
- What did ArcSight find in Backstage (packages/ui)?
- src/types: fan-in 24, blast radius 252, CRITICAL. 301 modules and 916 dependency edges traced.
- Why does the Backstage (packages/ui) structure matter?
- In Backstage (packages/ui), Change-risk signal at src/types (fan-in 24) — merge impact can travel beyond the diff you see. Blast radius on src/types reaches 252 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 Backstage (packages/ui)?
- Start with src/types. 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.
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>Evidence-backed analysis snapshot. Validation record · Install · Homepage demo