burpsuite-project-parser

# Burp Suite project parser ## Contract | Field | Bound contract | |---|---| | Trigger | A user asks to search or analyze a Burp Suite .burp project, extract audit items, inspect targeted request or response metadata, or search captured traffic. | | Authority | Read-only. No file, VCS, credential, paid, published, deployed, or remote mutation. The .burp project is read through Burp Suite Professional; no project file is modified. | | Side effect | The user-selected local .burp project is read through Burp Suite Professional, with output capped and filtered. | | Done | The requested operation returns relevant, size-checked JSON within record and byte limits, body fields are truncated to at most 1000 characters, and Burp findings are presented as indicators requiring validation rather than proof. | ## Inputs - Project file path (required): absolute path to a `.burp` project file. - Operation (required): one of `auditItems`, `proxyHistory`, `siteMap`, `responseHeader='regex'`, `responseBody='regex'`, or a sub-component filter such as `proxyHistory.request.headers`. - BURP_JAVA (required if not at default platform path): path to Burp Suite Professional's bundled Java executable. Defaults: macOS `/Applications/Burp Suite Professional.app/Contents/Resources/jre.bundle/Contents/Home/bin/java`; Linux `/opt/BurpSuiteProfessional/jre/bin/java`. - BURP_JAR (required if not at default platform path): path to `burpsuite_pro.jar`. Defaults: macOS `/Applications/Burp Suite Professional....