RustScan · Issues· 53 open
Open on GitHubLocally synced open issues (discussions stay on GitHub)
- #933
UDP port scanner is missing SNMP ports
Updated Sep 17, 2026 - #795
When used with the `--port` option, lot of noisy output is generated
Updated Sep 6, 2026 - #825
Question: Proxies not supported?
Updated Aug 27, 2026 - #686
Make Kali Linux Pack
good first issueUpdated Aug 27, 2026 - #706
Rustcan API Library is too noisy in stdout
good first issueUpdated Jul 13, 2026 - #864
why im running in rustscan cant with flag, error like "[!] Error Exit code = 1" ? (can in nmap itself)
Updated Mar 26, 2026 - #741
use $XDG_CONFIG_HOME for default config file path
Updated Mar 18, 2026 - #862
[!] Error Exit code = 127 When Running rustscan (Even Without Nmap Flags)
Updated Feb 10, 2026 - #775
There are bugs in the output results using nmap
Updated Feb 10, 2026 - #824
Using cargo install of 2.4.1 on Debian 12 - impossible to install because of env_logger version mismatch?
Updated Feb 10, 2026 - #683
Add ARM support for GitHub actions
good first issueUpdated Jan 31, 2026 - #800
RustScan built from 2.4.1 tag reports version 2.3.0 due to outdated version in Cargo.toml
Updated Dec 26, 2025 - #780
Support for port range input like `1-22,661-669,8888` for both CLI and library usage
Updated Dec 25, 2025 - #835
Hope to support port string and range combination parameters
Updated Nov 27, 2025 - #829
Identify TCP/UDP ports. Append /tfor TCP or /ufor UDP to the IP address (e.g., 1.1.1.1/u, 2.2.2.2/t).
Updated Sep 15, 2025