Here's Express.js (the npm package, 141 files). Scanned in 551ms on a laptop:
- 1,953 components extracted
- 17,505 typed dependencies mapped (not just "A calls B" — ownership, injection, weak ref, circular, etc.)
- 25 architectural blocks detected automatically
- 498 architectural smells found
- 116 dead code detections
- 100% classification consensus (zero ambiguous)
Component distribution:
Core logic: 425 (21.8%) — app, router, route objects
Terminals: 744 (38.1%) — constants, test assertions
Helpers: 346 (17.7%) — utility functions
State stores: 313 (16.0%) — express, request, Router, factories
Features: 110 (5.6%) — test-specific app instances
Middleware: 10 (0.5%) — andRestrictTo, sendfile
Entry points: 5 (0.3%) — users, restrict, getCookie
Architectural problems detected:
CRITICAL: 532 components in circular dependency chains
ERROR: God Class — `app` has 67 outbound dependencies
ERROR: God Class — `router` has 83 outbound dependencies
Stateful services at 0% health (critical coupling)
Cross-cutting concerns found automatically:
trust proxy logic in request.js (8 components)
response callback chain: onend, onaborted, onerror, onfinish
pure functions — 71 components, 93% health
boundary validators — 98% health
All of this is known to be true by anyone who's worked on Express.
The God Object pattern in `app` is a documented community concern.
The circular deps between app↔router↔request↔response are well-known.
551ms. No LLM. No cloud. Deterministic — same input, same output, every time.
Happy to run it against any public repo if you want to suggest one.
