← HomepageAll repository proofValidation recordState of TS Architecture 2026
Repository proof
What ArcSight found in Effect
Real arc impact on Effect (packages/effect) — blast radius, break paths, and evidence. Same question as the homepage: what breaks if I change this?
Project: Effect (packages/effect) · Score: 44.3/100 (High architecture risk) · 363 modules · 3,365 edges
arc impact src/FunctionRun 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.
Architecture score & metrics
Score: 44.3/100 · Stability: 1/100 · Status: critical · Confidence: 100%
- Dependency cycles: 100+
- Duplicate authorities: 311
Architectural gravity centers
src/Types— concentrates too many responsibilitiessrc/Types— shared utility hubsrc/Function— concentrates too many responsibilitiessrc/Function— shared utility hubsrc/Predicate— concentrates too many responsibilities
Try it in the terminal
Simulated arc analyze output from the dataset. No analysis runs in the browser.
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 breaksarc scanFind issuesarc fixApply fixesarc finishResolve remainingarc watchKeep clean
- Score
- 44.3
- Modules
- 363
- Edges
- 3,365
Metrics
| Metric | Value |
|---|---|
| Architecture score | 44.3/100 |
| Modules | 363 |
| Edges | 3,365 |
| Dependency cycles | 100+ |
FAQ
- What did ArcSight find in Effect (packages/effect)?
- Effect (packages/effect) has 363 modules and an architecture score of 44.3/100.
- Why does the Effect (packages/effect) structure matter?
- The Effect (packages/effect) score is 44.3/100 across 363 modules and 3,365 edges.
- Which file should I inspect first in Effect (packages/effect)?
- Start with src/Function. 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.
Embed this report
Use this iframe to show the architecture badge on your site.
<iframe src="https://arcsight.ai/embed/effect/" width="320" height="180" frameborder="0"></iframe>Explore
Evidence-backed analysis snapshot. Validation record · Install · Homepage demo