dscan
open-sourceThe section your link pointed to isn't on dscan's page any more, so we've brought you to the top.
dscan is a distributed Nmap scanner that wraps Nmap and distributes scans across several hosts.
Summary
dscan is an open-source command-line wrapper around nmap that distributes port scans and asset discovery across multiple hosts using a server-agent architecture, and it costs nothing to use. You install it via pip, generate a self-signed certificate, then run one host as the server holding a target list and others as agents that pull tasks from it, tracking scan stages and completion through a status table. This suits network administrators or red teamers who need to spread scans over several machines rather than run nmap from a single box. The project dates to 2020, has had five tracked releases from two contributors, but shows no commits in the past year, so treat it as dormant rather than actively maintained.
dscan is a distributed Nmap scanner that wraps Nmap and distributes scans across several hosts.
How dscan helps
Which hosts across my whole target list are actually up and reachable, without running one box flat out?
splits the target file into discovery tasks that agents pull down and run their own nmap scans against, so the work is spread across however many agents connect
Which ports and services are open across a large network I've split among several scan machines?
agents pull scan stages from the server one at a time and hand nmap results back, so a multi-host sweep produces one consolidated view instead of separate per-machine outputs
How far along is a scan that's spread across several agents, and what's still outstanding?
the server keeps a status table showing stage counts, pending tasks, and completion percentage per stage, refreshed as agents report task status
Which agent is responsible for scanning a given target right now?
the status table lists each connected agent alongside the stage and target IP it's currently working on, so a stalled or slow target can be traced to a specific machine
Did every stage of a distributed scan run to completion, or did some targets get dropped?
the per-stage breakdown shows targets versus finished counts, so a stage stuck below full completion flags targets that never got scanned
Languages
Command line
| option | found in | since | description |
|---|
Values are placeholders taken from each option’s declared default. Nothing is executed here — the output shown is a recording of a run that already happened.
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
- Community health
-
Contributor trend distinct committers, this year against last
-
Maintainer concentration bus factor now against a year ago
-
Issue backlog trend issues closed per issue opened, 12 months
-
Responsiveness median time to a maintainer’s first reply
Nine scores for dscan, 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 → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
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 dscan 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…
Releases
Nothing shipped since we started watching. Releases and docs updates land here as they happen.
Project health
Issue, contributor and maintainer activity in 0x4E0x650x6F/dscan, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 0 −1 vs prior 12 months
- Maintainers 0 +0 joined · −1 left, last 12 months
- Bus factor 0 committers behind half the commits
- Community-filed not measured of issues opened, last 12 months
- Median time to close not measured issues closed, last 12 months
- Open backlog not measured open issues today
- Issues opened / month not measured
- Open backlog not measured
- Contributors / month 0
- Commits / month 0
- Stars 20
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
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.
Choose a badge style and copy the code →