What ArcSight found
src/types: fan-in 21, blast radius 28, MEDIUM. 40 modules and 104 dependency edges traced.
← HomepageAll repository proofValidation recordState of TS Architecture 2026
Repository proof
What ArcSight found in Turborepo
Real arc impact on Turborepo (packages/turbo-codemod) — blast radius, break paths, and evidence. Same question as the homepage: what breaks if I change this?
Project: Turborepo (packages/turbo-codemod) · Score: 93.7/100 (Excellent architecture) · 40 modules · 104 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/types21 dependents
- src/runner18 dependents
- src/utils/get-transformer-helpers14 dependents
- src/utils/load-turbo-json9 dependents
- src/runner/types3 dependents
- src/runner/runner2 dependents
- src/utils/logger2 dependents
- src/runner/file-transform1 dependents
- src/types28 modules
- src/runner28 modules
- src/runner/runner28 modules
- src/utils/logger28 modules
- src/utils/get-transformer-helpers17 modules
- src/utils/load-turbo-json9 modules
| Module | Fan-in | Blast | Risk |
|---|---|---|---|
| src/types | 21 | 28 | MEDIUM |
| src/runner | 18 | 28 | MEDIUM |
| src/runner/runner | 2 | 28 | LOW |
| src/utils/logger | 2 | 28 | CRITICAL |
| src/utils/get-transformer-helpers | 14 | 17 | CRITICAL |
| src/utils/load-turbo-json | 9 | 9 | CRITICAL |
| src/runner/types | 3 | LOW | |
| src/runner/file-transform | 1 | LOW |
Why it matters
In Turborepo (packages/turbo-codemod), Change-risk signal at src/types (fan-in 21) — merge impact can travel beyond the diff you see. Blast radius on src/types reaches 28 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/runner
- src/runner/runner
What evidence supports it
- Local CLI analysis — repository source stays on your machine
- Structural coverage: 40 modules, 104 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: 93.7/100 · Stability: 50/100 · Status: healthy · Confidence: 100%
- Dependency cycles: 2
- Duplicate authorities: 5
Architectural gravity centers
src/types— concentrates too many responsibilitiessrc/types— sits on a dependency cyclesrc/types— shared utility hubsrc/runner— concentrates too many responsibilitiessrc/runner— sits on a dependency cycle
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
- 93.7
- Modules
- 40
- Edges
- 104
Metrics
| Metric | Value |
|---|---|
| Architecture score | 93.7/100 |
| Modules | 40 |
| Edges | 104 |
| Dependency cycles | 2 |
FAQ
- What did ArcSight find in Turborepo (packages/turbo-codemod)?
- src/types: fan-in 21, blast radius 28, MEDIUM. 40 modules and 104 dependency edges traced.
- Why does the Turborepo (packages/turbo-codemod) structure matter?
- In Turborepo (packages/turbo-codemod), Change-risk signal at src/types (fan-in 21) — merge impact can travel beyond the diff you see. Blast radius on src/types reaches 28 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 Turborepo (packages/turbo-codemod)?
- Start with src/types. Run arc impact on that file before the change merges.
Key takeaways
- •Architecture score 93.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/turborepo/" width="320" height="180" frameborder="0"></iframe>Evidence-backed analysis snapshot. Validation record · Install · Homepage demo