nmap

Right now, whenever Zenmap crashes, it gives the user a stack trace and asks the user to send it to the Nmap dev list. So we get a flood of emails (most of which aren't even allowed through moderation) which often contain just a stack trace with no subject line or any explanatory text in the message body. Lots of these are for well known issues in older versions of Zenmap. So it's not very usef

RustScan has an accessible mode, rustscan --accessible which should promise not to have any weird ASCII text in it.

Write CI that runs RustScan with --accessible a few times, with different flags / options and check the terminal output to see if it contains one of these:

1. [!]
2. [~]
3. [>]
4. | {}

If any of these characters appear in any of the tests, fail the CI. E

There's a border case when the amount of items in the input file are lower than the number of instances in a given fleet.

For example, we want to run a scan using all nuclei templates on 20 urls having a fleet with 40 machines.
This situation will output the following error cat: input: No such file or directory because 20 instances are receiving empty input files.

Desired behavior

The current view is "15 Most Common Product/Ports"
Only seeing 15 Products limits the visibility into network recon.

Request is to add the option to "Show All Products Ports"
The ability to see all products is key to network enumeration.

![image](https

Hi,

Appreciate sharing this stylesheet with us.

I am encountering a visual error. As you can see 2 ports are open, however they are not reported in the summary table.

Also for some reason the IP is reported multiple times

Nice project! One nice-to-have would be support of the -oX parameter. I see the option to output in greppable format (-oG) but not XML.