Do I have to supply all five inputs?

Yes. The tool requires --httpx, --naabu, --nuclei, --sslyze, and --webanalyze. For a scanner your workflow skipped, pass an empty file, or for --sslyze a file containing {"server_scan_results": []}. The report then covers only sources that returned data.

How does it use the nuclei JSON output?

Pass nuclei JSONL through --nuclei. The node reads template-id, severity, matcher name, and extracted results, then files them under the matched host in a scans block so vulnerabilities sit with ports and tech for that target.

What does the merged report look like?

One YAML block per target host. Each host lists open ports, then a servers list where every entry carries ip, url, status_code, detected tech, any nuclei scans with severity, and any sslyze TLS weaknesses. Ordering stays stable so two runs diff cleanly.

Where does the merged YAML report land?

The managed node writes a file and a folder output. Connect the five JSON inputs; you do not set a separate output path on the CLI.

Updated Jul 14, 2026

Utilities

Fold five scanner JSON streams into one host-keyed YAML

Merge five scanner JSON streams into one host-keyed YAML report.

Automate a pentest scan report Correlate findings per host Hand a reviewer one readable artifact

overview

What generate-yaml-report does

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

Where generate-yaml-report fits

Automate a pentest scan report

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.

Correlate findings per host

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.

Hand a reviewer one readable artifact

Give an analyst structured YAML they can skim or diff between runs, rather than opening and cross-referencing five raw tool outputs by hand.

Feed downstream automation

Emit one predictable document a ticketing script, notifier, or storage step can parse, instead of wiring each scanner's native format separately.

reference

generate-yaml-report inputs and flags

5 inputs

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

Run generate-yaml-report

generate-yaml-report · command

# 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.yaml

sample output

example.com:  servers:    - ip: 203.0.113.10      url: https://example.com      status_code: 200      tech:        - nginx      scans:        - template: CVE-2021-26855          severity: high

guidance

Choosing generate-yaml-report

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.

batch-output

Slices a list into line ranges. Splits input; this node merges scanner output.

nuclei

Produces the vulnerability JSON this node consumes. Run it upstream, not instead of the report.

httpx

Produces the HTTP JSON this node folds in. An input to the report, not a substitute.

faq

generate-yaml-report questions

Five: httpx, naabu, nuclei, sslyze, and webanalyze. Pass each JSON with --httpx, --naabu, --nuclei, --sslyze, and --webanalyze. The node merges them into one YAML document keyed by target host.

Run generate-yaml-report yourself

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.

Open generate-yaml-report in the library Build a workflow with it

Facts on this page come from the live Trickest tool library.