How over-flowy/typexplorer works
Project type and purpose
• This is a Burp Suite extension (plugin) written in Python (via Jython).
• Purpose: automate sending a single HTTP request with multiple Content-Type headers (URL-encoded, JSON, XML, etc.), collect all responses, and display them in a split-pane UI for quick vulnerability checks (CSRF, IDOR, ATO).
File structure
• Top-level files:
• TypeXplorer.py – the entire extension code (registers with Burp, defines UI, handlers, test-case generator).
• README.md – describes installation, usage, features.
• assets/ – UI screenshots (for documentation), possibly other static resources.
• No separate frontend/backend folders since it is a single-file plugin loaded into Burp.
• No build scripts – runtime is handled by Burp + Jython.
README for additional insights
• The extension plugs into Burp’s context menu (“Send to TypeXplorer”).
• It keeps an internal list of endpoints; each endpoint, when selected, can be deleted or re-triggered.
• UI is a two-pane Swing interface (request list on one side, response details on the other).
• Uses Jython standalone JAR to run inside Burp.
Final recommendations
• UI layer is shown as a separate concern but within the same process.
• Avoid over-partitioning; focus on the extension’s five or six core modules rather than dozens of tiny functions.