What ArcSight found
src/utils: fan-in 16, blast radius 18, LOW. 24 modules and 122 dependency edges traced.
← HomepageAll repository proofValidation recordState of TS Architecture 2026
Repository proof
What ArcSight found in TanStack Query
Real arc impact on TanStack Query (packages/query-core) — blast radius, break paths, and evidence. Same question as the homepage: what breaks if I change this?
Project: TanStack Query (packages/query-core) · Score: 81.7/100 (Healthy architecture) · 24 modules · 122 edges
arc impact src/utilsRun 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/utils16 dependents
- src/types15 dependents
- src/queryClient11 dependents
- src/query9 dependents
- src/notifyManager9 dependents
- src/subscribable8 dependents
- src/mutation6 dependents
- src/queryObserver5 dependents
- src/utils18 modules
- src/types18 modules
- src/queryClient18 modules
- src/query18 modules
- src/mutation18 modules
- src/queryObserver18 modules
- src/environmentManager18 modules
- src/mutationCache18 modules
| Module | Fan-in | Blast | Risk |
|---|---|---|---|
| src/utils | 16 | 18 | LOW |
| src/types | 15 | 18 | LOW |
| src/queryClient | 11 | 18 | LOW |
| src/query | 9 | 18 | CRITICAL |
| src/mutation | 6 | 18 | CRITICAL |
| src/queryObserver | 5 | 18 | CRITICAL |
| src/environmentManager | 4 | 18 | CRITICAL |
| src/mutationCache | 4 | 18 | CRITICAL |
| src/notifyManager | 9 | LOW | |
| src/subscribable | 8 | LOW |
Why it matters
In TanStack Query (packages/query-core), Change-risk signal at src/utils (fan-in 16) — merge impact can travel beyond the diff you see. Blast radius on src/utils reaches 18 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/utils
- src/types
- src/queryClient
What evidence supports it
- Local CLI analysis — repository source stays on your machine
- Structural coverage: 24 modules, 122 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: 81.7/100 · Stability: 29/100 · Status: healthy · Confidence: 100%
- Dependency cycles: 35
- Layer violations: 1
- Duplicate authorities: 4
Architectural gravity centers
src/utils— concentrates too many responsibilitiessrc/utils— sits on a dependency cyclesrc/utils— shared utility hubsrc/utils— crosses a layer boundarysrc/types— 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
- 81.7
- Modules
- 24
- Edges
- 122
Metrics
| Metric | Value |
|---|---|
| Architecture score | 81.7/100 |
| Modules | 24 |
| Edges | 122 |
| Dependency cycles | 35 |
FAQ
- What did ArcSight find in TanStack Query (packages/query-core)?
- src/utils: fan-in 16, blast radius 18, LOW. 24 modules and 122 dependency edges traced.
- Why does the TanStack Query (packages/query-core) structure matter?
- In TanStack Query (packages/query-core), Change-risk signal at src/utils (fan-in 16) — merge impact can travel beyond the diff you see. Blast radius on src/utils reaches 18 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 TanStack Query (packages/query-core)?
- Start with src/utils. Run arc impact on that file before the change merges.
Key takeaways
- •Architecture score 81.7/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/tanstack/" width="320" height="180" frameborder="0"></iframe>Evidence-backed analysis snapshot. Validation record · Install · Homepage demo