nfdump
v1.7.9 open-sourceThe section your link pointed to isn't on nfdump's page any more, so we've brought you to the top.
nfdump is a suite of tools for collecting, processing, and analyzing NetFlow, IPFIXIPFIXAn IETF standard protocol for exporting network flow records from routers and probes to a collector, giving cyber tools a vendor-neutral stream of structured traffic metadata without full packet capture., and sFlow data from network devices.
nfdump -r /flow_base_dir/router1/nfcapd.202501011200 -A srcasn,dstasn ./configure --enable-lto nfanon -W 4 input.pcap sfcapd -X "flow_id,custom_metric" -i eth0 nfdump -r flow.nf 'srcport >= 80 and srcport <= 443' nfdump -r flow.nf 'nip in [ 2001:db8::1, 2001:db8::2 ]' nfpcapd -i eth0 -o /path/to/output/dir nfdump -R /data -o json:json_bz2
Summary
nfdump is an open-source suite of command-line tools for collecting, processing, and analyzing NetFlow, IPFIX, and sFlow data from network devices, free to use. It runs as a collector daemon (nfcapd/sfcapd) that writes flow files to disk, with the nfdump client used to filter, aggregate, and convert that data using tcpdump-like filter syntax, outputting to text, CSV, JSON, or ndjson. It suits network and security analysts who need to inspect traffic patterns or investigate incidents from flow records rather than full packet capturespacket capturesA packet capture, recorded network packets that can be inspected later. Analysts use it to reconstruct communication and investigate protocol behavior or suspicious traffic., and it integrates with NfSen and with monitoring stacks via metrics export to InfluxDB or Prometheus. The project traces back to 2015 and remains active, with 62 contributors, 279 commits and 16 releases in the past year, and a last release only 26 days ago.
nfdump is a suite of tools for collecting, processing, and analyzing NetFlow, IPFIX, and sFlow data from network devices.
How nfdump helps
Which hosts talked to which other hosts, and how much traffic passed between them?
filters collected flow records by address, port, or protocol and reports matching flows with their byte and packet counts, without needing a packet capture of the traffic
Which autonomous systems are sending or receiving the most traffic on this network?
aggregates flows by source and destination ASN and produces per-AS traffic summaries
Is any of this traffic touching a Tor exit node?
enriches flow records against a Tor exit-node database so matching source or destination addresses are flagged in the output
Where geographically are these connections coming from or going to?
enriches flow records with geolocation data drawn from a GeoDB/Maxmind database and can tag the router or exporter address with its geo location in the output
Did last week's traffic pattern look different from this week's?
reads two sets of collected flow files with the same filter and aggregation and reports the matching flows from each, so the resulting byte and packet counts can be compared
How do I get flow records into a format my monitoring stack can ingest?
writes filtered or aggregated results as text, CSV, or JSON, or through a user-defined output format, instead of only its own binary layout
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 nfdump, 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 nfdump 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
24 entries
No entries match these filters.
- September 20261
- July 20267
- April 20261
- November 20251
- April 20251
- October 20241
- February 20241
- September 20231
- April 20231
- December 20221
- September 20221
- May 20211
- November 20201
- August 20201
- August 20191
- May 20181
- November 20171
- January 20161
Project health
Issue, contributor and maintainer activity in phaag/nfdump, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 3 −5 vs prior 12 months
- Maintainers 1 +0 joined · −0 left, last 12 months
- Bus factor 1 committers behind half the commits
- Community-filed 89% of issues opened, last 12 months
- Median time to close 5 days first maintainer reply 18 hours
- Open backlog 4 of 507 issues ever filed
- Issues opened / month 1 · 1 communitymaintainers
- Open backlog 4
- Contributors / month 1
- Commits / month 7
- Stars 920
- bugs 17%
- features 22%
- questions 17%
- other 44%
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
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.