Netcap
v0.13.0 open-sourceThe section your link pointed to isn't on Netcap's page any more, so we've brought you to the top.
Netcap converts network packets into structured Protocol Buffer audit records designed for security monitoring, forensic analysis, and machine learning.
./net capture -read traffic.pcap --service --dns-resolution-context ./net capture -read traffic.pcap --service --evidence-links --evidence-links-window 30m --evidence-links-max-links 100 sudo ./net capture -iface en0 -dpi-workers 4 net agent -gen-keypair -cert agent.crt -key agent.key net agent -cert agent.crt -key agent.key -server-fingerprint <collector-sha256> -flush-interval 2s net util -download-dbs net util -index all make test-wireshark net capture -read ot-traffic.pcap --dnp3-point-map points.csv NC_DNP3_POINT_MAP=/etc/netcap/points.csv sudo net capture -iface eth0 ./net capture -read ot-traffic.pcap --rules rules/examples/s7comm_hunt.yml --approved-workstations 10.0.1.50,10.0.1.51 ./net capture --service --service-preload-dir /data/forensics/pcaps net util -decoders net util -download-dbs netcap publish-module <module_path> netcap dump --json -o output.json netcap -r traffic.pcap -payload netcap -r traffic.pcap --decode-option default
Summary
Netcap is an open-source network-analysis tool, distributed under GPLv3, that converts captured network packets into structured, type-safe Protocol Buffer audit records for security monitoring, forensic analysis, and machine learning. It runs as a single Go binary on the command line, with 83 packet decoders and 40+ stream decoders covering everything from TLS and HTTP/2 to industrial protocols like Modbus and S7Comm, and it ships a built-in web UI for the forensic analysts, threat hunters, and OT security teams who need to inspect traffic rather than just alert on it. It sits in the packet-capture and traffic-classification space, pairing deep packet inspection (nDPInDPIAn open-source deep packet inspection library maintained by ntop that classifies network traffic by protocol and application, giving cyber tools visibility into what flows are actually carrying beyond port numbers./libprotoident) with a rule engine for detection logic and IOCIOCAn indicator of compromise, an observable clue that may point to malicious activity, such as a suspicious file hash or domain. It is evidence to investigate, rather than proof by itself. lookups, and it now includes an MCPMCPModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. server for LLMLLMA large language model, a neural network trained on large amounts of text to recognize patterns and generate language. Applications use it for tasks such as answering, summarizing and writing code.-driven PCAPPCAPA packet capture, recorded network packets that can be inspected later. Analysts use it to reconstruct communication and investigate protocol behavior or suspicious traffic. analysis. With 245 commits and 19 releases in the past year, the most recent just 12 days ago, it is under active development.
Netcap converts network packets into structured Protocol Buffer audit records designed for security monitoring, forensic analysis, and machine learning.
How Netcap helps
Which protocols and services were actually in this capture, beyond what the port numbers suggest?
classifies traffic with nDPI and libprotoident deep packet inspection and writes the detected application into the relevant audit record, catching cases where a service runs on a non-standard port
Which hosts in this capture talked to known-bad infrastructure?
matches connection records against IOC databases pulled from the hosted or self-hosted database service and flags the matching audit records
Is there a beaconing or scanning pattern hiding in this traffic?
the detection rule engine tracks source-to-distinct-destination fan-out and record-time thresholds and reports sources that cross them, using time-of-day helpers to separate off-hours activity from business-hours noise
Which files moving across the wire are worth a closer look?
extracts files from reassembled streams and runs YARA and Magika against them to identify file types and flag malware matches
Is a workstation on this network one that was never approved?
checks connection sources against an approved-workstation allowlist through a rule-engine expression helper and surfaces any host missing from it
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 Netcap, 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 Netcap 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
20 entries
No entries match these filters.
- October 20263
- September 20263
- April 20261
- October 20253
- January 20221
- September 20211
- August 20211
- February 20202
- November 20191
- October 20191
- May 20191
- January 20191
- December 20181
Project health
Issue, contributor and maintainer activity in dreadl0ck/netcap, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 1 −1 vs prior 12 months
- Maintainers 1 +1 joined · −1 left, last 12 months
- Bus factor 1 committers behind half the commits
- Community-filed 33% of issues opened, last 12 months
- Median time to close 2 days first maintainer reply 4.5 days
- Open backlog 0 of 22 issues ever filed
- Issues opened / month 0 · 0 communitymaintainers
- Open backlog 0
- Contributors / month 1
- Commits / month 141
- Stars 1,802
- other 100%
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.