What did ArcSight find in Trigger.dev (packages/trigger-sdk)?

Trigger.dev (packages/trigger-sdk) has 49 modules and an architecture score of 92.7/100.

Why does the Trigger.dev (packages/trigger-sdk) structure matter?

The Trigger.dev (packages/trigger-sdk) score is 92.7/100 across 49 modules and 93 edges.

Which file should I inspect first in Trigger.dev (packages/trigger-sdk)?

Start with src/v3/tracer. Run arc impact on that file before the change merges.

← Homepage All repository proof Validation record State of TS Architecture 2026

Repository proof

What ArcSight found in Trigger.dev

Real arc impact on Trigger.dev (packages/trigger-sdk) — blast radius, break paths, and evidence. Same question as the homepage: what breaks if I change this?

Project: Trigger.dev (packages/trigger-sdk) · Score: 92.7/100 (Excellent architecture) · 49 modules · 93 edges

arc impact src/v3/tracer

Install ArcSight →Why trust ArcSight →

Run 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.

Dependency graph for this codebase — Dependency graph

Subsystem architecture for this codebase — Subsystem architecture

Architecture score & metrics

Score: 92.7/100 · Stability: 61/100 · Status: healthy · Confidence: 100%

Duplicate authorities: 19

Architectural gravity centers

src/v3/tracer— concentrates too many responsibilities
src/v3/tracer— shared utility hub

Try it in the terminal

Simulated arc analyze output from the dataset. No analysis runs in the browser.

ArcSight CLI (simulated)

$ arc scan trigger

Architecture Score: 92.7

Modules: 49

Cycles: 0

Hotspots: 10

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 breaks
arc scanFind issues
arc fixApply fixes
arc finishResolve remaining
arc watchKeep clean

More commands (explain, guard…) →

Trigger.dev (packages/trigger-sdk) architecture metrics

Score: 92.7
Modules: 49
Edges: 93

Metrics

Metric	Value
Architecture score	92.7/100
Modules	49
Edges	93

FAQ

What did ArcSight find in Trigger.dev (packages/trigger-sdk)?: Trigger.dev (packages/trigger-sdk) has 49 modules and an architecture score of 92.7/100.
Why does the Trigger.dev (packages/trigger-sdk) structure matter?: The Trigger.dev (packages/trigger-sdk) score is 92.7/100 across 49 modules and 93 edges.
Which file should I inspect first in Trigger.dev (packages/trigger-sdk)?: Start with src/v3/tracer. Run arc impact on that file before the change merges.

Key takeaways

•Architecture score 92.7/100 indicates a healthy structure with room to reduce cycles and violations.
•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.

npm install -g arcsight

arc impact <path>

Install ArcSight →

Embed this report

Use this iframe to show the architecture badge on your site.

<iframe src="https://arcsight.ai/embed/trigger/" width="320" height="180" frameborder="0"></iframe>

Explore

LanguageCategoryModular MonolithHigh CouplingCompareLeaderboard

Evidence-backed analysis snapshot. Validation record · Install · Homepage demo