You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think the JSON output should be NDJSON, as it is for a lot of other tools (Zgrab2 / Zdns, Masscan, Nuclei / dnsx / httpx, etc.).
What it means is that instead of having one really long line:
[{"result": 1}, {"result": 2}, {"result": 3}]
You would have one line per result:
{"result": 1}
{"result": 2}
{"result": 3}
The main advantage for tools parsing your result is that they could read the results line per line, instead of having to json.load() the whole result at once, storing it in memory.
You could take advantage of this to write the result as soon as they are available (as you do for the text output from what I understand). This would:
save a lot of memory since currently the whole JSON stays in the RAM before writing the result file;
allow interrupted scans to still produce exploitable results.
What do you think?
The text was updated successfully, but these errors were encountered:
Hi there,
I think the JSON output should be NDJSON, as it is for a lot of other tools (Zgrab2 / Zdns, Masscan, Nuclei / dnsx / httpx, etc.).
What it means is that instead of having one really long line:
You would have one line per result:
The main advantage for tools parsing your result is that they could read the results line per line, instead of having to
json.load()
the whole result at once, storing it in memory.You could take advantage of this to write the result as soon as they are available (as you do for the text output from what I understand). This would:
What do you think?
The text was updated successfully, but these errors were encountered: