PAGES
← all tools
◆ Reconnaissance & OSINT

naabu

v2.7.0 open-source

Naabu is a port scanning tool written in Go that enumerates valid ports for hosts using fast SYN/CONNECT/UDPUDPA network protocol that sends individual messages without guaranteeing delivery or order. Applications trade built-in reliability for less overhead and can add their own recovery. scans.

Summary

Naabu is an open-source, MIT-licensed port scanner written in Go, run from the command line, that performs SYN, CONNECT, and UDP scans to enumerate open ports on a host or list of hosts quickly. It accepts input as STDIN, a single host, IP, CIDRCIDRA notation for a block of IP addresses, such as 10.0.0.0/24. The number after the slash says how many leading address bits identify the network. block, or ASNASNAutonomous System Number — a globally unique identifier assigned by regional internet registries to a network operator, letting routing protocols distinguish which organization controls a block of IP addresses., outputs to JSON, text, or STDOUT, and can hand results to Nmap for service detection or pipe them into other tools like httpx, which suits red teamers and reconnaissance engineers mapping attack surfaceattack surfaceThe exposed systems, interfaces and access points an attacker could try to use. It includes internet-facing services as well as identities, software and other reachable resources. rather than analysts investigating a single incident. It sits in the network reconnaissance space, alongside other host-discovery and scanning utilities rather than one named competitor, and is built for chaining into larger recon pipelines. Started in 2020 and maintained by ProjectDiscovery, it has 85 contributors, roughly 190 commits and 20 releases in the past year, with a release only 108 days ago, indicating active upkeep.

Naabu is a port scanning tool written in Go that enumerates valid ports for hosts using fast SYN/CONNECT/UDP scans.

How naabu helps

Which hosts on this network segment are actually alive and reachable?

runs a discovery scan across a host, CIDR block, or ASN and lists the ones that respond, before any port-level work begins

Which ports are actually open on these hosts right now?

sends SYN, CONNECT, or UDP probes to each target and reports every port that replies, rather than relying on a static assumption of what should be listening

What service and version is running behind an open port I found?

hands the discovered ports to Nmap for service detection, returning the fingerprint instead of just a bare port number

Can I find exposed ports on a target without sending it any traffic myself?

queries Shodan's Internetdb for previously observed open ports on an IP, giving a passive answer when a live probe isn't an option

Am I scanning the same set of live hosts twice when the input is a list of domains?

resolves DNS first and deduplicates by IP automatically, so one host behind several names is only scanned once

How do I get open-port results into the next stage of my recon pipeline?

writes results as JSON, plain text, or STDOUT so they can be piped directly into tools like httpx for follow-on probing

all 19 features, with the evidence for each →

Languages

Not documented

Features

19 capabilities across 7 capability groups · 7 backed by code, an API document or a real run

Built from naabu's releases, docs, README and our own runs. “Seen” marks the month we first spotted a release the vendor didn't date. Group names and tags are our labels.

Compare with peers →

  • naabu covers 7 of the 13 network discovery and scanning capabilities we track.

What naabu offers you

  • Command-line interface4
  • CSV data export1
Attack surface inventory 4 features Network discovery and scanning since 2020
Shodan InternetDB integration verified Queries the Shodan InternetDB API to retrieve known open-port data for a target, reporting lookup failures as warnings rather than fatal errors. 2 releases · 4 other sources · first seen Mar 2022

Shared capability: Attack surface inventory

release

  • Adds -passive flag to enable passive port enumeration via Shodan's InternetDB API v2.0.7 · May 2022 · source · release history
  • Adds timestamp field to JSON output for better auditability v2.0.6 · Mar 2022 · source · release history

we ran it

  • The tool attempted to query https://internetdb.shodan.io/dvwa but failed because no address could be resolved for the hostname dvwa. No port data was returned. Aug 2026 · the full run
  • The tool attempted to query https://internetdb.shodan.io/dvwa but failed because no address could be resolved for the hostname dvwa. No open ports were returned. Aug 2026 · the full run

example

  • Perform passive scanning against a target using Shodan's data instead of active network probes. naabu -passive -host example.com v2.0.7 · May 2022 · source
  • Pipe a list of hosts directly into naabu for stream processing. cat hosts.txt | naabu -stream v2.0.6 · Mar 2022 · source
Nmap integration shipped Allows using Nmap as the backend scanning engine or piping output directly into Nmap for further enumeration. 1 release · 2 other sources · first seen Dec 2020

Shared capability: Attack surface inventory

release

  • Adds -nmap-cli flag to run nmap directly on Naabu's output v2.0.3 · Dec 2020 · source · release history

example

  • Fingerprint services on the top 1000 ports of a target, using the embedded nmap probes and limiting workers for a controlled scan. naabu -host example.com -top-ports 1000 -sV -sV-workers 10 -sV-timeout 10s -json -o results.json v2.7.0 · Oct 2026 · source
  • Pipe Naabu's IP output directly into nmap for further service enumeration without intermediate files. naabu -host example.com | xargs -I{} nmap -Pn {} v2.0.3 · Dec 2020 · source
ASN-based Scanning shipped Scans all IP addresses associated with a specified Autonomous System number. 1 release · 1 other source · first seen Oct 2022

Shared capability: Attack surface inventory

release

  • Added ASN input support to scan all IPs in a given Autonomous System number v2.1.1 · Oct 2022 · source · release history

example

  • Scan all IP addresses associated with a specific Autonomous System number. echo AS15133 | naabu v2.1.1 · Oct 2022 · source
Multi-IP scanning shipped Scans all resolved IP addresses for a given hostname, supporting hosts with multiple aliases or IPs. 1 release · 1 other source · first seen Dec 2020

Shared capability: Attack surface inventory

Also counts toward: Command-line interface

release

  • Adds -scan-all-ips flag to scan multiple IPs of the same host v2.0.3 · Dec 2020 · source · release history

example

  • Scan all resolved IP addresses for a hostname, useful when you need to cover all aliases. naabu -scan-all-ips example.com v2.0.3 · Dec 2020 · source
Port scanning 2 features Network discovery and scanning since 2020
Predictive port scanning verified Uses a port-correlation model to predict and prioritise which ports are likely open, with a configurable confidence threshold. 5 releases · 7 other sources · first seen Sep 2020

Shared capability: Port scanning

Also counts toward: Command-line interface

release

  • Adds predictive scanning to anticipate and prioritize likely open ports during discovery. v2.6.0 · Apr 2026 · source · release history
  • Adds stream mode input support allowing hosts to be piped into naabu via stdin v2.0.6 · Mar 2022 · source · release history
  • Adds comma-separated host input, allowing multiple IPs/domains in a single target argument v2.0.6 · Mar 2022 · source · release history
  • Adds rate limit control via packet count per second configuration v2.0.2 · Sep 2020 · source · release history
  • Adds network interface selection support to choose which NIC is used for scanning v2.0.2 · Sep 2020 · source · release history

command line

  • -prediction-threshold — minimum confidence for port predictions (0-100%) (default 20) v2.6.0 · Apr 2026 · command-line history
  • -smart-scan — predictive port scanning using port correlation model v2.6.0 · Apr 2026 · command-line history
  • --smart-scan — predictive port scanning using port correlation model v2.6.0 · Apr 2026 · command-line history

we ran it

  • The tool loaded a correlation model (814 source ports, 3315 correlations, 20% threshold) and scanned 100 ports across the single host over two retries. It found 1 open port: dvwa:80. Aug 2026 · the full run
  • The tool loaded a model of 814 source ports and 3315 correlations at a 20% threshold, scanned 100 ports across the single host over two retries, and found one open port: dvwa:80. Aug 2026 · the full run

example

  • Pipe a list of hosts directly into naabu for stream processing. cat hosts.txt | naabu -stream v2.0.6 · Mar 2022 · source
  • Limit scan speed to 1000 packets per second to avoid triggering rate limits on target infrastructure. naabu --host example.com -rate 1000 v2.0.2 · Sep 2020 · source
Scan Filtering and Thresholds shipped Filters results based on port count thresholds to exclude hosts with fewer than N open ports. 2 releases · first seen Oct 2022

Shared capability: Port scanning

release

  • Adds dynamic result filtering to refine port scan output on the fly. v2.3.5 · Jul 2025 · source · release history
  • Added -pts flag to exclude hosts with fewer than N open ports v2.1.1 · Oct 2022 · source · release history
UDP port scanning 2 features Network discovery and scanning since 2025
UDP Payload Probing shipped Enables active UDP service probing by sending custom payloads during port scanning. 2 releases · 2 other sources · first seen Nov 2025

Shared capability: UDP port scanning

release

  • Adds -uP / -udp-probes flag to send protocol-specific payloads on UDP scans using nmap-service-probes. v2.7.0 · Oct 2026 · source · release history
  • Adds UDP payload support, enabling active probing of UDP services during port scanning. v2.3.6 · Nov 2025 · source · release history

example

  • Run a UDP scan with protocol-specific payloads to identify UDP services on common ports. naabu -host 192.168.1.0/24 -p 53,161,500,4500 -s SYN -uP -json v2.7.0 · Oct 2026 · source
  • UDP scan with protocol-specific probes naabu -host scanme.sh -p u:53,u:123,u:161 -uP
UDP port scanning verified Supports UDP port scanning when UDP ports are specified and nmap-service-probes is available, warning when prerequisites are missing. 4 other sources · first seen Aug 2026

Shared capability: UDP port scanning

docs

  • Fast port scanner written in Go that performs SYN/CONNECT/UDP scans on hosts and enumerates open ports.

we ran it

  • The tool found 1 open port on dvwa: port 80. Three warnings were emitted: no UDP ports were specified so -uP has no effect, the nmap-service-probes file could not be found so UDP probes could not be… Aug 2026 · the full run

example

  • Scan specific ports including UDP naabu -p 80,443,21-23,u:53 -host hackerone.com
  • UDP scan with protocol-specific probes naabu -host scanme.sh -p u:53,u:123,u:161 -uP
TCP port scanning 1 feature Network discovery and scanning since 2020
TCP port scanning verified Scans hosts for open TCP ports, automatically falling back to a CONNECT scan when running without root privileges. 7 releases · 27 other sources · first seen Sep 2020

Shared capability: TCP port scanning

release 7 total

  • Enables SYN scan support on Windows via npcap, bringing raw-packet scanning to Windows hosts. v2.6.0 · Apr 2026 · source · release history
  • Supports reading port lists from a file, enabling reusable and shareable port scope definitions. v2.3.6 · Nov 2025 · source · release history
  • -p flag now works with [host|ip]:port input (e.g., echo google.com:443 | naabu -silent) to target specific ports directly v2.1.7 · Aug 2023 · source · release history
  • Adds SOCKS5 proxy support via the -proxy flag v2.0.6 · Mar 2022 · source · release history
  • Adds customizable stats interval via the -si flag v2.0.6 · Mar 2022 · source · release history
  • Adds -s flag to select scan type (SYN, CONNECT) v2.0.3 · Dec 2020 · source · release history

docs

  • Fast port scanner written in Go that performs SYN/CONNECT/UDP scans on hosts and enumerates open ports.

we ran it 17 total

  • The tool found 1 open port on the host dvwa: port 80. It ran a CONNECT scan due to non-root privileges and exited with status 0, indicating successful completion. Aug 2026 · the full run
  • The tool found 1 open port on the host dvwa: port 80. It ran a CONNECT scan due to non-root privileges, and the exit status 0 indicates successful completion. Aug 2026 · the full run
  • One open port was found: TCP port 80 on host dvwa, with TLS reported as false. The tool ran a CONNECT scan (non-root mode) and the exit status 0 confirms successful completion. Aug 2026 · the full run
  • The tool found 1 open port on the host dvwa: port 80. It ran a CONNECT scan (indicating non-root execution) and exited with status 0, meaning the scan completed successfully. Aug 2026 · the full run
  • The tool found 1 open port on the host dvwa: port 80. Two warnings were emitted — host discovery normally requires a SYN scan, but because the process lacked root privileges, naabu automatically… Aug 2026 · the full run
  • The tool found 1 open port on the host dvwa: port 80. It ran a CONNECT scan due to non-root privileges and exited with status 0, indicating successful completion. Aug 2026 · the full run

example 9 total

  • Run a SYN scan on Windows (requires npcap installed) to get accurate port results without relying on connect-scan fallbacks. naabu -host 192.168.1.0/24 -s syn -p 80,443,8080,8443 v2.6.0 · Apr 2026 · source
  • Force scanning port 80 on an IP that might otherwise be skipped or scanned differently echo 142.250.183.174:443 | ./naabu -silent -p 80 v2.1.7 · Aug 2023 · source
  • Scan a specific port on a host directly without needing a text file list echo google.com:443 | ./naabu -silent v2.1.7 · Aug 2023 · source
  • Perform a TCP connect scan instead of the default SYN scan against target hosts. naabu -s CONNECT -host example.com v2.0.3 · Dec 2020 · source
  • Use Nmap as the backend scanner for compatibility with specific nmap scripts or behaviors. naabu --host example.com --nmap v2.0.2 · Sep 2020 · source
  • Fast port scan of a host naabu -host example.com
TCP connect scanning 1 feature Network discovery and scanning since 2023
Proxy Support shipped Routes scanning traffic through SOCKS5 or HTTP proxies for anonymity or network constraints. 1 release · 1 other source · first seen Feb 2023

Shared capability: TCP connect scanning

Also counts toward: Command-line interface

release

  • Adds --proxy flag to route connect scans through a SOCKS5 or HTTP proxy v2.1.2 · Feb 2023 · source · release history

example

  • Run a connect scan through a proxy server. naabu --proxy socks5://127.0.0.1:9050 -host example.com v2.1.2 · Feb 2023 · source
Network host discovery 1 feature Network discovery and scanning since 2022
Host Discovery shipped Performs network mapping to identify live hosts before initiating port scanning. 4 releases · 2 other sources · first seen Jul 2022

Shared capability: Network host discovery

release

  • Adds -show-dead flag to report hosts that did not respond during host discovery (requires host discovery to be enabled). v2.7.0 · Oct 2026 · source · release history
  • Adds a confidence level indicator for IPs skipped because the host discovery threshold was exceeded, giving clearer signal on scan coverage gaps. v2.3.2 · Oct 2024 · source · release history
  • Added additional probes for host discovery v2.2.0 · Nov 2023 · source · release history
  • host-discovery support for network mapping before port scanning v2.0.8 · Jul 2022 · source · release history

example

  • Discover live hosts in a CIDR and surface dead hosts that did not respond, useful for asset inventory gaps. naabu -host 10.0.0.0/24 -sn -show-dead -silent v2.7.0 · Oct 2026 · source
  • Point naabu to a custom configuration directory during execution. naabu -config /path/to/custom/config.yaml -host example.com v2.3.0 · Mar 2024 · source
Service and version detection 1 feature Network discovery and scanning since 2026
Service version detection verified Attempts to identify service versions on open ports using nmap-service-probes, skipping the step gracefully when the probe file is not available. 3 releases · 3 other sources · first seen Mar 2026

Shared capability: Service and version detection

release

  • Adds -sV / -service-version flag for native service version detection using embedded nmap-service-probes, with -sV-fast to probe only port-hinted services, -sV-timeout to control probe timeout, -sV-workers for concurrency, and -sV-probes to supply a custom nmap-service-probes file… v2.7.0 · Oct 2026 · source · release history
  • Adds -sV-fast mode that skips fallback probes and only targets port-hinted services for faster fingerprinting. v2.7.0 · Oct 2026 · source · release history
  • Adds CPE (Common Platform Enumeration) field to service detection results when using Nmap integration, enabling richer asset fingerprinting. v2.5.0 · Mar 2026 · source · release history

we ran it

  • The tool found 1 open port — dvwa:80 — but could not perform service-version detection because nmap-service-probes was not found on the system; the warning advises installing nmap or supplying the… Aug 2026 · the full run
  • The tool found 1 open port — TCP 80 on dvwa — but service version detection was skipped entirely because nmap-service-probes could not be located; the -sV flag had no effect. Aug 2026 · the full run

example

  • Run nmap service detection on results echo hackerone.com | naabu -nmap-cli 'nmap -sV -oX nmap-output'
Other / not yet classified 7 features Features we have not matched to a capability yet. A suggested match is marked.
Structured output verified suggested Reports discovered open ports in structured formats including CSV, with fields for host, IP, port, protocol, TLS status, CDN status, and timestamp. 11 releases · 7 other sources · first seen Sep 2020

Suggested capability: Attack surface inventory. This is our guess, not confirmed.

Also counts toward: CSV data export

release 11 total

  • Adds DisableStdout option to the Go SDK to suppress stdout output when embedding naabu programmatically. v2.4.0 · Jan 2026 · source · release history
  • Allows specifying a custom asset ID to tag scan results for integration with asset management workflows. v2.3.6 · Nov 2025 · source · release history
  • Adds MAC address support to scan output, surfacing hardware-layer host identity alongside IP results. v2.3.6 · Nov 2025 · source · release history
  • Privileged scans now include the open_ports field in JSON output listing detected open ports v2.1.7 · Aug 2023 · source · release history
  • CDN information included in output for filtering and context v2.0.8 · Jul 2022 · source · release history
  • Adds CSV output format via -o csv flag v2.0.6 · Mar 2022 · source · release history

we ran it

  • The tool found 1 open port on the host dvwa — port 80 — but also logged that the threshold was reached and the scan was skipped for that host's IP. The run exited with status 0, indicating success. Aug 2026 · the full run
  • The tool found 1 open port on the host dvwa: port 80. No CDN information was reported in the output. The run completed with exit status 0, indicating success. Aug 2026 · the full run
  • The tool found 1 open port on the host dvwa: port 80/tcp, with TLS and CDN both reported as false. Aug 2026 · the full run
  • The tool found 1 open port on the host dvwa: port 80/tcp, with TLS and CDN both reported as false. The CSV output line contains several empty trailing fields. Aug 2026 · the full run

example

  • Suppress naabu's stdout when using it as a Go library — useful when integrating into a pipeline that owns its own output formatting. opts := &naabu.Options{ DisableStdout: true, // other options... } v2.4.0 · Jan 2026 · source
  • Include MAC addresses in JSON output to correlate open ports with hardware identifiers on a local network segment. naabu -host 10.0.0.0/24 -json | jq '{ip: .ip, mac: .mac, port: .port}' v2.3.6 · Nov 2025 · source
  • Exclude CDN ranges from scanning to focus only on origin infrastructure. naabu --host example.com -exclude-cdn v2.0.2 · Sep 2020 · source
DNS resolution verified Resolves target hostnames using configurable DNS ordering and an optional system-resolver fallback. 5 releases · 8 other sources · first seen Oct 2021

release

  • Supports DNS resolution over SOCKS5 proxies, keeping all traffic — including DNS — through the proxy. v2.6.0 · Apr 2026 · source · release history
  • Adds configurable DNS resolution order via -dns-order flag, controlling whether DNS queries go to local resolvers, the proxy, or both in a specified sequence. v2.6.0 · Apr 2026 · source · release history
  • Adds -ptr option to enable optional reverse DNS lookups on discovered ports v2.1.2 · Feb 2023 · source · release history
  • nmap integration in passive scan mode for richer data collection v2.0.8 · Jul 2022 · source · release history
  • Adds --custom-resolvers flag to accept a file of custom DNS resolvers for port scanning v2.0.5 · Oct 2021 · source · release history

command line

  • -dns-order — dns resolution order (p/l/lp/pl) (default "l") v2.6.0 · Apr 2026 · command-line history
  • --system-resolver — use system DNS as fallback resolver v2.6.0 · Apr 2026 · command-line history
  • -system-resolver — use system DNS as fallback resolver v2.6.0 · Apr 2026 · command-line history

example

  • Route all DNS queries through a SOCKS5 proxy during a scan — useful when targeting internal hosts only reachable via a jump proxy. naabu -host 10.10.10.0/24 -proxy socks5://127.0.0.1:1080 -dns-order pl v2.6.0 · Apr 2026 · source
  • Perform a scan and resolve hostnames for open ports. naabu -ptr -host example.com v2.1.2 · Feb 2023 · source
  • Scan all IP addresses associated with a specific Autonomous System number. echo AS15133 | naabu v2.1.1 · Oct 2022 · source
  • Use a private DNS infrastructure for internal asset discovery without leaking queries to public DNS. naabu --host example.com --custom-resolvers ./my-resolvers.txt v2.0.5 · Oct 2021 · source
  • Scan ports from a list of hosts naabu -list hosts.txt
Platform Support shipped Provides compilation and binary support for additional operating systems and processor architectures. 4 releases · first seen Jan 2025

release

IP Version Selection shipped suggested Explicitly selects the IP protocol version (IPv4 or IPv6) for scanning operations. 4 releases · first seen Jul 2022

Suggested capability: Port scanning. This is our guess, not confirmed.

Also counts toward: Command-line interface

release

  • IPv6 is now the default scan mode; workflows that relied on IPv4-only behavior may produce different results or require explicit configuration to restrict scans to IPv4. v2.4.0 · Jan 2026 · source · release history
  • Enables IPv6 scanning by default, broadening host coverage without extra flags. v2.4.0 · Jan 2026 · source · release history
  • IP Version selection via --ip-version flag v2.0.8 · Jul 2022 · source · release history
  • IPv6 port scan support for modern networks v2.0.8 · Jul 2022 · source · release history
Automatic Updates shipped Checks for and applies binary updates automatically to keep the tool current. 3 releases · 1 other source · first seen Mar 2023

release

  • Supports human-readable time formats for the timeout flag (e.g., 5s, 100ms, 1m) instead of bare integers. v2.3.4 · Jan 2025 · source · release history
  • -config string allows specifying a path to the naabu configuration file instead of the default $HOME/.config/naabu/config.yaml v2.3.0 · Mar 2024 · source · release history
  • Adds the -update flag to enable automatic binary updates and version checks. v2.1.3 · Mar 2023 · source · release history

example

  • Use millisecond-precision timeouts when scanning behind a slow proxy or tuning fast internal scans. naabu -host 10.0.0.0/24 -timeout 250ms v2.3.4 · Jan 2025 · source
Scan Resumption shipped Allows resuming interrupted scans from a previous state using a dedicated flag and state file. 1 release · 1 other source · first seen Mar 2022

release

  • Adds --resume flag to resume paused or interrupted scans using a state file v2.0.6 · Mar 2022 · source · release history

example

  • Continue a scan that was previously interrupted by providing the state file from the -resume flag. naabu -l targets.txt --resume resume.state v2.0.6 · Mar 2022 · source
Scan Health Monitoring shipped Provides flags to monitor the stability and health of the tool during long-running scans. 1 release · first seen Jul 2022

release

  • health-check flag for monitoring tool stability during long scans v2.0.8 · Jul 2022 · source · release history

Lines in monospace are the tool's own words: help text parsed from its source, or an endpoint from its API document. Under release, a line is our summary of a dated release. Under docs, it is quoted from the tool's own documentation or website. Each links back to the source it came from.

Score card

  1. Shipping velocity releases a month, last 12 months
  2. Documentation quality release-notes rubric, 0–100
  3. Breaking-change discipline how rarely a release breaks users, and notice given
  4. Maintenance risk quiet time against its own cadence, maintainers
  5. Innovation & surface new capabilities, API and MCP surface
  6. Community health
  7. Contributor trend distinct committers, this year against last
  8. Maintainer concentration bus factor now against a year ago
  9. Issue backlog trend issues closed per issue opened, 12 months
  10. Responsiveness median time to a maintainer’s first reply

Nine scores for naabu, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.

Score cards are part of every paid plan.

See plans →

Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.

How this is scored
  • Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
  • Documentation quality — the release-notes rubric published on the analytics page, unchanged.
  • Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
  • Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
  • Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
  • Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
  • Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
  • Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.

Release-note detail over time

See how much detail naabu puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.

Checking release-note history…

Explore the full chart →

Commercials

pricing & packaging history · ProjectDiscovery vendor page

23 readings of ProjectDiscovery's pricing page since Feb 2024, with 7 relaunches of its plan lineup and 4 changes to what its plans include — each one dated, compared with the reading before it, and explained for someone buying the tool.

Pricing and packaging history is included with Researcher and Business. See how every vendor we track sells, and how that has changed over time, using data we don't publish anywhere else.

See plans →

Website history

projectdiscovery.io, every change

ProjectDiscovery's home page and 3 more pages as they looked each month from August 2021 to October 2026: 18 renders, 4 changes of tagline or palette. Step through them, play them, or put any two months side by side.

Website history is included with Researcher and Business.

See plans →

Releases

Show

20 entries

  1. October 20261
  2. April 20261
  3. March 20261
  4. January 20261
  5. November 20251
  6. July 20251
  7. January 20251
  8. October 20241
  9. March 20241
  10. November 20231
  11. August 20231
  12. March 20231
  13. February 20231
  14. October 20221
  15. July 20221
  16. May 20221
  17. March 20221
  18. October 20211
  19. December 20201
  20. September 20201
    Show

    20 entries

    Project health

    Issue, contributor and maintainer activity in projectdiscovery/naabu, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.

    1. Contributors 23 +2 vs prior 12 months
    2. Maintainers 2 +2 joined · −3 left, last 12 months
    3. Bus factor 1 committers behind half the commits
    4. Community-filed 77% of issues opened, last 12 months
    5. Median time to close 9.1 days first maintainer reply 2.3 days
    6. Open backlog 0 of 431 issues ever filed
    1. Issues opened / month 0 · 0 communitymaintainers
    2. Open backlog 0
    3. Contributors / month 0
    4. Commits / month 0
    5. Stars 6,248
    Issue themes, last 12 months
    • bugs 45%
    • features 18%
    • other 37%

    Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this

    Articles

    1 article · updated Nov 4, 2026

    Where naabu turns up in what others publish: how-tos, attack reports that name it, and incident write-ups. A row says why it is here and quotes where the article names it; the link goes to the publisher.

    Breach post-mortems & incident response 1

    Libraries its release ships

    What its latest release locks, checked against known advisories.

    None of its release's images build from a lockfile we can read.

    Add the badge to your README

    Maintain this project? The badge links readers straight to this page, so they can follow every release here.

    Tracked by Cyber Toolchain Choose a badge style and copy the code →
    browse all tools → score card for your toolchain →