← HomepageAll repository proofValidation recordState of TS Architecture 2026
Repository proof
What ArcSight found in Temporal TypeScript SDK
Real arc impact on Temporal TypeScript SDK (packages/workflow) — blast radius, break paths, and evidence. Same question as the homepage: what breaks if I change this?
Project: Temporal TypeScript SDK (packages/workflow) · Score: 93/100 (Excellent architecture) · 26 modules · 81 edges
arc impact src/global-attributesRun 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: 93/100 · Stability: 41/100 · Status: healthy · Confidence: 100%
- Dependency cycles: 10
- Duplicate authorities: 1
Architectural gravity centers
src/global-attributes— concentrates too many responsibilitiessrc/global-attributes— sits on a dependency cyclesrc/global-attributes— shared utility hub
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
- 93
- Modules
- 26
- Edges
- 81
Metrics
| Metric | Value |
|---|---|
| Architecture score | 93/100 |
| Modules | 26 |
| Edges | 81 |
| Dependency cycles | 10 |
FAQ
- What did ArcSight find in Temporal TypeScript SDK (packages/workflow)?
- Temporal TypeScript SDK (packages/workflow) has 26 modules and an architecture score of 93/100.
- Why does the Temporal TypeScript SDK (packages/workflow) structure matter?
- The Temporal TypeScript SDK (packages/workflow) score is 93/100 across 26 modules and 81 edges.
- Which file should I inspect first in Temporal TypeScript SDK (packages/workflow)?
- Start with src/global-attributes. Run arc impact on that file before the change merges.
Key takeaways
- •Architecture score 93/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/temporal-typescript/" width="320" height="180" frameborder="0"></iframe>Explore
Evidence-backed analysis snapshot. Validation record · Install · Homepage demo