clistats UI improvements

[ehsandeep]

To avoid excessive output in the terminal, here are a few possible option that we can opt for in future development.

• Stable solution that works on keypress (as planned initially)
• Printing the output in a single line ( didn’t worked out initially)
• Something else?

[geeknik]

I like the idea of a tmux or screen style line that sits at the bottom of the console and the relevant nuclei output streams above it. Of course, if that doesn't work again, maybe nuclei needs a stats API so that we can run a third party app like shox or barely. Of course there are also plenty of third party progress bars that could be pillaged (with credit of course) for their usefulness: pb, progressbar, mpb, uiprogress, multibar or echelon.

[geeknik]

A suggestion for -stats as it is right now: Replacing the Templates: ### with the template ID being used by nuclei at that time?

[sw33tLie]

IMO this should be done ffuf-style (so the second option).
A simple bar at the bottom with updated data seems just perfect to me.

[ehsandeep]

A suggestion for -stats as it is right now: Replacing the Templates: ### with the template ID being used by nuclei at that time?

Stats are printed after each 5 seconds and multiple templates get executed at the same time, so it's not possible to sync stats with running template ID.

[geeknik]

Stats are printed after each 5 seconds and multiple templates get executed at the same time, so it's not possible to sync stats with running template ID.

Hmm, I've seen this done in other places. Impossible just means nobody has written the right code yet. (;

Also, the Hosts: counter in the current iteration of -stats is incorrect. It counts the same host more than once if it has an open port on 80, 443, 8080, 8443, etc. IMO, only the number of unique hosts being tested, not the number of ports being tested should be displayed. Maybe the documentation could be updated to reflect this?