What ArcSight found
src/types/job-options: fan-in 5, blast radius 46, MEDIUM. 95 modules and 277 dependency edges traced.
← HomepageAll repository proofValidation recordState of TS Architecture 2026
Repository proof
What ArcSight found in BullMQ
Real arc impact on BullMQ — blast radius, break paths, and evidence. Same question as the homepage: what breaks if I change this?
Project: BullMQ · Score: 94/100 (Excellent architecture) · 95 modules · 277 edges
arc impact src/types/job-optionsRun 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/interfaces22 dependents
- src/enums17 dependents
- src/types15 dependents
- src/utils14 dependents
- src/classes/job10 dependents
- src/classes/redis-connection9 dependents
- src/interfaces/redis-client8 dependents
- src/types/job-options5 dependents
- src/types/job-options46 modules
- src/interfaces/redis-client38 modules
- src/enums35 modules
- src/interfaces/telemetry34 modules
- src/types32 modules
- src/interfaces27 modules
- src/classes/errors/connection-closed-error25 modules
- src/utils21 modules
| Module | Fan-in | Blast | Risk |
|---|---|---|---|
| src/types/job-options | 5 | 46 | MEDIUM |
| src/interfaces/redis-client | 8 | 38 | CRITICAL |
| src/enums | 17 | 35 | CRITICAL |
| src/interfaces/telemetry | 5 | 34 | CRITICAL |
| src/types | 15 | 32 | CRITICAL |
| src/interfaces | 22 | 27 | CRITICAL |
| src/classes/errors/connection-closed-error | 5 | 25 | CRITICAL |
| src/utils | 14 | 21 | CRITICAL |
| src/classes/redis-connection | 9 | 14 | CRITICAL |
| src/classes/job | 10 | 13 | CRITICAL |
| src/interfaces/backoff-options | 3 | MEDIUM | |
| src/interfaces/parent-options | 3 | MEDIUM | |
| src/interfaces/repeat-options | 3 | MEDIUM | |
| src/types/keep-jobs | 3 | MEDIUM |
Why it matters
In BullMQ, Change-risk signal at src/types/job-options (fan-in 5) — merge impact can travel beyond the diff you see. Blast radius on src/types/job-options reaches 46 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/job-options
- src/interfaces/redis-client
- src/enums
What evidence supports it
- Local CLI analysis — repository source stays on your machine
- Structural coverage: 95 modules, 277 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: 94/100 · Stability: 47/100 · Status: healthy · Confidence: 100%
- Dependency cycles: 1
- Duplicate authorities: 6
Architectural gravity centers
src/enums— concentrates too many responsibilitiessrc/types— concentrates too many responsibilitiessrc/types— depends on an unstable modulesrc/interfaces— concentrates too many responsibilitiessrc/interfaces— depends on an unstable module
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
- 94
- Modules
- 95
- Edges
- 277
Metrics
| Metric | Value |
|---|---|
| Architecture score | 94/100 |
| Modules | 95 |
| Edges | 277 |
| Dependency cycles | 1 |
FAQ
- What did ArcSight find in BullMQ?
- src/types/job-options: fan-in 5, blast radius 46, MEDIUM. 95 modules and 277 dependency edges traced.
- Why does the BullMQ structure matter?
- In BullMQ, Change-risk signal at src/types/job-options (fan-in 5) — merge impact can travel beyond the diff you see. Blast radius on src/types/job-options reaches 46 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 BullMQ?
- Start with src/types/job-options. Run arc impact on that file before the change merges.
Key takeaways
- •Architecture score 94/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/bullmq/" width="320" height="180" frameborder="0"></iframe>Evidence-backed analysis snapshot. Validation record · Install · Homepage demo