lsof
4.99.7 open-sourceThe section your link pointed to isn't on lsof's page any more, so we've brought you to the top.
Lists open files and the processes that opened them on Unix-like systems.
lsof -i UDP -T s lsof -j -p 1234 | jq 'select(.type == "REG") | .name' lsof -J > open_files_snapshot.json lsof -i UDP -T ./lsof -p $$ -a -d fd ./lsof -r c10
Summary
lsof is an open-source command-line utility that lists open files and the processes holding them open on Unix-like systems, and it costs nothing to use. It runs as a single command you invoke against a PID or the whole system, making it a staple for Linux and BSD/Darwin administrators, incident responders, and SOCSOCA security operations center, the team or function that monitors threats, investigates alerts and coordinates incident response. Its work can be internal, outsourced or shared. analysts who need to see what a process has open right now. Recent work lets it emit JSON or JSON Lines output instead of its traditional tabular format, so results can be piped through jq or ingested directly into a SIEMSIEMSecurity information and event management, collecting logs from many systems and correlating events to find suspicious activity. Analysts use it to investigate alerts and incidents. like Splunk or Elastic, and it can show 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. socket connection states on Linux for spotting sockets stuck in unexpected states during an incident. It sits in the category of core Unix diagnostic utilities rather than competing with any named product. First committed in 2018, it has 75 contributors and remains active, with 83 commits in the past year and a release 66 days ago.
Lists open files and the processes that opened them on Unix-like systems.
How lsof helps
What is holding this file open so I can't unmount the disk?
lists every process with the file open, showing its command name, PID, user, and the exact path from the process's file descriptor table
Which process is this port or socket actually bound to?
scans a process's file descriptor table for network sockets and reports the associated command and PID, letting a UDP socket's connection state be read directly on Linux to spot ones stuck unconnected or unexpectedly established
What shared libraries is this running process actually using right now?
walks the memory-mapped region entries in a process's open file list and prints the full path of each loaded library, reflecting what is actually mapped rather than what was requested at launch
Can I feed a snapshot of every open file on this box into my SIEM without writing a parser?
emits the full system-wide listing as one JSON object per process or as JSON Lines with one object per open file, so it can be piped through jq or ingested directly by Splunk or Elastic
Which processes still have deleted or stale files open, keeping disk space from being freed?
reports files whose directory entry is gone as still-open descriptors, and on Linux treats NFS files left stale after a server-side change as unlinked so they can be selected and cleared
Which user or working directory does this running process belong to?
reads the process's current working directory and root directory entries alongside its user ID from the same file descriptor table, in the same listing as its open files
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 lsof, 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 lsof 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
60 entries
No entries match these filters.
- June 20262
- March 20261
- December 20231
- November 20231
- January 20232
- April 20221
- November 20201
- February 20181
- October 20141
- January 20131
- April 20121
- September 20111
- July 20101
- October 20081
- April 20081
- April 20061
- August 20051
- May 20051
- March 20041
- January 20041
- June 20031
- March 20031
- June 20021
- April 20021
- March 20021
- January 20021
- October 20011
- September 20011
- July 20011
- May 20011
- February 20011
- December 20001
- November 20001
- June 20001
- April 20001
- November 19991
- October 19991
- May 19991
- February 19991
- January 19991
- July 19981
- April 19981
- March 19981
- February 19982
- December 19972
- November 19971
- October 19972
- September 19971
- August 19971
- June 19972
- May 19971
- April 19971
- March 19972
Project health
Issue, contributor and maintainer activity in lsof-org/lsof, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 17 +12 vs prior 12 months
- Maintainers 2 +1 joined · −0 left, last 12 months
- Bus factor 1 committers behind half the commits
- Community-filed 100% of issues opened, last 12 months
- Median time to close 513 days first maintainer reply 5.3 hours
- Open backlog 17 of 127 issues ever filed
- Issues opened / month 0 · 0 communitymaintainers
- Open backlog 17
- Contributors / month 2
- Commits / month 2
- Stars 574
- 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.