Nettacker
0.4.1 open-sourceThe section your link pointed to isn't on Nettacker's page any more, so we've brought you to the top.
OWASPOWASPA nonprofit foundation that publishes open standards, guides, and ranked vulnerability lists—most famously the OWASP Top 10—giving cyber tools a vendor-neutral benchmark to test or report against. Nettacker is an open-source, Python-based automated penetration testing framework for reconnaissance, vulnerability assessments, and network security audits.
nettacker -d -i target.com --subdomain-list targets.txt nettacker -i target.com -m dir_scan nettacker -g <target> -m citrix_cve_2023_24488_vuln nettacker -g <target> -m moveit_version_scan
Summary
Nettacker is an open-source, Apache-licensed penetration testing and reconnaissance framework, run mostly from the command line though it also ships a web UI, that automates port scanning, service detection, subdomain enumeration, network mapping, vulnerability scanning and credential brute-forcing. It is built for cyber security professionals and ethical hackers who need to survey networks, web applications, IoTIoTA collective label for internet-connected physical devices — sensors, cameras, routers, appliances — that tools target because they run embedded firmware with limited patching and broad network exposure. devices and APIs for weaknesses rather than test one target by hand, and options like scan comparison and API allow-listing point to use in repeatable, automated audits rather than one-off manual testing. It sits in the same space as general-purpose recon and pentest frameworks, covering ground that might otherwise mean stitching together separate scanning and brute-forcing tools. Under the OWASP umbrella since 2017, it has 91 contributors and remains active, with 115 commits and 10 releases in the past year.
OWASP Nettacker is an open-source, Python-based automated penetration testing framework for reconnaissance, vulnerability assessments, and network security audits.
How Nettacker helps
Which hosts on this network are alive, and what services are running on them?
sweeps the address range and reports open ports and identified services host by host, so the full footprint is visible in one pass instead of one host at a time
Which subdomains exist for a domain that nobody told you about?
enumerates subdomains from certificate transparency and other discovery sources and lists what resolves, surfacing forgotten or shadow assets
Do any of these logins accept weak or reused credentials?
runs brute-force checks against services like SMB and web logins with supplied or default wordlists and reports which accounts and services accepted them
Which known vulnerabilities affect the services this scan found?
matches discovered services and versions (including things like CUPS, Jenkins, SmarterMail, CrushFTP, Adobe AEM) against its vulnerability checks and reports which targets are affected
Did this week's scan open up anything that last week's didn't?
compares two saved scan results and reports the differences, so a new port, service, or finding stands out instead of being buried in a full report
Can these results feed straight into the vulnerability tracker or CI pipeline the rest of the team already uses?
writes results out as SARIF or DefectDojo-compatible JSON alongside its own report formats, so findings drop into existing review or tracking tools without reformatting
Languages
Command line
No command matches.
| 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 Nettacker, 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 Nettacker 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
5 entries
No entries match these filters.
- August 20261
- September 20241
- January 20241
- October 20231
- July 20231
Project health
Issue, contributor and maintainer activity in OWASP/Nettacker, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 26 +7 vs prior 12 months
- Maintainers 4 +2 joined · −1 left, last 12 months
- Bus factor 2 committers behind half the commits
- Community-filed 94% of issues opened, last 12 months
- Median time to close 2.9 days first maintainer reply 2.4 days
- Open backlog 104 of 410 issues ever filed
- Issues opened / month 10 · 0 communitymaintainers
- Open backlog 104
- Contributors / month 4
- Commits / month 7
- Stars 5,572
- bugs 7%
- features 0%
- questions 2%
- other 91%
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.