@ehsandeep @dogancanbakir @Mzack9999 Hi, are there any update about this?

@0x123456789 Thanks for opening this PR. Katana was mostly thought as an active crawler (it discover and visit nodes), which is different from a passive crawler (simply discover nodes). This difference becomes important when the maximum depth is reached, since it's that particular phase where nodes can be discovered in the last responses, but are not visited due to maximum depth constraint. The crawler output consists of a request sent/response received, hence probably these endpoints can still be sent in the queue and printed to the output, but we need to add a new attribute to mark that the endpoints are just discovered but not visited, I'll try to implement a generic mechanism for this in your PR.

Closing as not planned for the time being as not visited results above the depth threshold would be erroneously enqueued for further visiting