Platform Architecture
The current v4 runtime layers: desktop, daemon, transport, session, attacks, store, evidence, and validation.
Platform Architecture
WSHawk v4 is organized around a local runtime with clear layers instead of one monolithic scanner process.
Main Layers
| Layer | Purpose | |---|---| | Desktop | Electron operator interface | | Bridge / Daemon | local HTTP and Socket.IO service layer | | Transport | HTTP and WebSocket proxying and traffic capture | | Session | browser capture, replay helpers, identity handling | | Attacks | replay, AuthZ diff, race, and related services | | Protocol | graphing, inference, templates, target packs | | Store | project-backed local persistence | | Evidence | bundles, timeline, export, integrity metadata | | Validation | local benchmark labs and expected outcomes |
Route Groups
The daemon is split into route groups so workflow responsibilities stay clearer:
- platform routes
- transport routes
- system routes
- scan routes
- web routes
CLI Compatibility
The top-level CLI still exists, but the strongest v4 path is the desktop plus local daemon plus project-backed services.