How hangga/webslurp works
WebSlurp is a Chrome DevTools extension for capturing, analyzing, editing, and replaying HTTP requests. The workflow starts in the DevTools panel, captures traffic from the inspected page, presents requests for filtering and editing, and replays requests for response inspection or concurrent race testing. Supporting layers hold shared state, parsing helpers, and persisted session/settings data. The README documents IDOR analysis and other security capabilities; sampled source does not expose every analysis path, so those connections are shown only where documented.
Main entry points: network.js Capture and replay · render.js Request and response view · panel.js Panel entry · storage.js Logs and settings
Components 15
DevTools panel
- Panel entry
panel.js - Request editor events
modules/events.js - Request and response view
modules/render.js - Request filtering
modules/filter.js
Capture and replay
- Capture and replay
modules/network.js
Analysis and inspection
- Security analysis
modules/security.js - Session refresh
modules/refresh.js
State and persistence
- Parsing helpers
modules/helpers.js - Shared UI and request state
modules/state.js - Logs and settings
modules/storage.js
Other components
- Security tester
- DevTools host
- Inspected page
- HTTP services
- Chrome local storage
Connections 24
- Security tester → DevTools host: opens panel
readme.md - DevTools host → Panel entry: loads panel
- Panel entry → Capture and replay: starts capture
panel.js - Inspected page → Capture and replay: provides traffic
readme.md - Capture and replay → Logs and settings: saves logs
modules/network.js - Capture and replay → Request and response view: refreshes list
modules/network.js - Capture and replay → Security analysis: checks authorization
modules/network.js - Capture and replay → HTTP services: sends requests
modules/network.js - Request and response view → Capture and replay: sends edited request
modules/render.js - Request and response view → Request filtering: filters logs
modules/render.js - Request and response view → Parsing helpers: formats details
modules/render.js - Request editor events → Logs and settings: persists edits
modules/events.js - Request editor events → Request and response view: rerenders detail
modules/events.js - Request editor events → Capture and replay: starts race test
modules/events.js - Panel entry → Logs and settings: imports and saves logs
panel.js - Panel entry → Session refresh: refreshes session
panel.js - Panel entry → Request and response view: renders list
panel.js - Session refresh → Logs and settings: loads logs
modules/refresh.js - Session refresh → Request and response view: renders session
modules/refresh.js - Logs and settings → Chrome local storage: reads and writes
modules/storage.js - Panel entry → Shared UI and request state: uses UI state
panel.js - Capture and replay → Shared UI and request state: uses request state
modules/network.js - Request and response view → Shared UI and request state: uses view state
modules/render.js - Security analysis → Request and response view: adds findings
readme.md