loading
Loading content
loading
Utilities
Merge five scanner JSON streams into one host-keyed YAML report.
overview
generate-yaml-report reads JSON from httpx, naabu, nuclei, sslyze, and webanalyze via --httpx, --naabu, --nuclei, --sslyze, and --webanalyze, then writes one YAML document keyed by target host. Ports, live HTTP, tech, nuclei hits, and TLS findings nest under the same host.
A recon run leaves five result files. This node is the converge step: open ports, HTTP probes, template matches, certificate issues, and tech fingerprints line up per host instead of staying scattered.
Wire the five JSON inputs at the tail of a recon pipeline; the managed Utilities node emits a file and folder a reviewer or the next step can consume.
use cases
End a recon-and-scan pipeline with one YAML file instead of collating httpx, naabu, nuclei, sslyze, and webanalyze output by hand, so every run produces the same report shape.
Line up open ports, live HTTP responses, detected technologies, nuclei matches, and TLS weaknesses under the same target so the full picture of a host sits in one block.
Give an analyst structured YAML they can skim or diff between runs, rather than opening and cross-referencing five raw tool outputs by hand.
Emit one predictable document a ticketing script, notifier, or storage step can parse, instead of wiring each scanner's native format separately.
reference
| Name | Type | Flag | Description |
|---|---|---|---|
| httpx-file | FILE | --httpx | httpx JSONL of live HTTP responses; keys the report and gives each host its ip, url, and status code. |
| naabu-file | FILE | --naabu | naabu JSONL of discovered open ports, listed per host. |
| nuclei-file | FILE | --nuclei | nuclei JSONL of template findings; each becomes a scan entry with template id and severity. |
| sslyze-file | FILE | --sslyze | sslyze JSON; flags TLS weaknesses like heartbleed, ROBOT, and CCS injection per host. |
| webanalyze-file | FILE | --webanalyze | webanalyze JSONL of detected technologies, attached to the matching URL. |
Showing key inputs. generate-yaml-report exposes 5 inputs in total.
example
# merge each scanner's JSON into one reportgenerate-yaml-report --httpx httpx.json --naabu naabu.json --nuclei nuclei.json --sslyze sslyze.json --webanalyze webanalyze.json --output report.yamlexample.com: servers: - ip: 203.0.113.10 url: https://example.com status_code: 200 tech: - nginx scans: - template: CVE-2021-26855 severity: highguidance
Use at the end of a recon workflow that produced httpx, naabu, nuclei, sslyze, or webanalyze JSON and you want one YAML document. It formats findings; it does not scan. Keep each tool's native output when you need raw streaming JSON.
Slices a list into line ranges. Splits input; this node merges scanner output.
Produces the vulnerability JSON this node consumes. Run it upstream, not instead of the report.
Produces the HTTP JSON this node folds in. An input to the report, not a substitute.
faq
related
Spider a URL and return a wordlist for password crackers.
Wordlist and mined-word subdomain permutation.
Import, export, and upsert workflow data against an Airtable base.
Decode Android APK files into smali sources and resources.
Check a file's values against conditions and exit with a matching code.
Authenticated Route53 hosted-zone inventory.
A host list feeds nuclei, whose JSON findings flow into generate-yaml-report, which merges them into a single YAML document written as the workflow's final output.
Facts on this page come from the live Trickest tool library.