burpsuite-project-parser — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited burpsuite-project-parser (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
This catalog copy contains the inline guidance below, but does not include the following supporting paths. They are external prerequisites, not bundled files:
scripts/burp-search.sh (wrapper; unavailable in this catalog tree)Ask for the original supporting material or an existing installation before using a step that depends on these paths; this catalog does not identify a verified download source for them. Resolve each path relative to that installation, inspect its contents, and verify any applicable license and execution prerequisites. Do not run a command or claim a referenced procedure was followed until its required file exists. Do not fabricate the missing scripts or treat an unrelated file with the same name as equivalent. Independent steps fully documented here can proceed within the user’s authorized scope; report any dependent step as unavailable.
Search and extract data from Burp Suite project files using the burpsuite-project-file-parser extension.
This skill delegates parsing to Burp Suite Professional - it does not parse .burp files directly.
Required:
Install the extension:
Use the wrapper script:
{baseDir}/scripts/burp-search.sh /path/to/project.burp [FLAGS]The script uses environment variables for platform compatibility:
BURP_JAVA: Path to Java executableBURP_JAR: Path to burpsuite_pro.jarSee Platform Configuration for setup instructions.
ALWAYS use sub-component filters instead of full dumps. Full proxyHistory or siteMap can return gigabytes of data. Sub-component filters return only what you need.
| Filter | Returns | Typical Size |
|---|---|---|
proxyHistory.request.headers | Request line + headers only | Small (< 1KB/record) |
proxyHistory.request.body | Request body only | Variable |
proxyHistory.response.headers | Status + headers only | Small (< 1KB/record) |
proxyHistory.response.body | Response body only | LARGE - avoid |
siteMap.request.headers | Same as above for site map | Small |
siteMap.request.body | Variable | |
siteMap.response.headers | Small | |
siteMap.response.body | LARGE - avoid |
Start with headers, not bodies:
# Header subset only; redact cookies, Authorization and other secrets before display
{baseDir}/scripts/burp-search.sh project.burp proxyHistory.request.headers | head -c 50000
{baseDir}/scripts/burp-search.sh project.burp proxyHistory.response.headers | head -c 50000
# BAD - full records include bodies, can be gigabytes
{baseDir}/scripts/burp-search.sh project.burp proxyHistory # NEVER DO THISOnly fetch bodies for specific URLs after reviewing headers, and ALWAYS truncate:
# 1. First, find interesting URLs from headers
{baseDir}/scripts/burp-search.sh project.burp proxyHistory.response.headers | \
jq -r 'select(.headers | test("text/html")) | .url' | head -n 20
# 2. Then search bodies with targeted regex - MUST truncate body to 1000 chars
{baseDir}/scripts/burp-search.sh project.burp "responseBody='.*specific-pattern.*'" | \
head -n 10 | jq -c '.body = (.body[:1000] + "...[TRUNCATED]")'HARD RULE: Body content > 1000 chars must NEVER enter context. If the user needs full body content, they must view it in Burp Suite's UI.
responseHeader='.*regex.*'Searches all response headers. Output: {"url":"...", "header":"..."}
Example - find server signatures:
responseHeader='.*(nginx|Apache|Servlet).*' | head -c 50000responseBody='.*regex.*'MANDATORY: Always truncate body content to 1000 chars max. Response bodies can be megabytes each.
# REQUIRED format - always truncate .body field
{baseDir}/scripts/burp-search.sh project.burp "responseBody='.*<form.*action.*'" | \
head -n 10 | jq -c '.body = (.body[:1000] + "...[TRUNCATED]")'Never retrieve full body content. If you need to see more of a specific response, ask the user to open it in Burp Suite's UI.
auditItemsReturns all sec
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.