The Sleuth Kit
sleuthkit-4.14.0 open-sourceThe section your link pointed to isn't on The Sleuth Kit's page any more, so we've brought you to the top.
Open source forensic toolkit for analyzing Microsoft and UNIX file systems and disk images to identify and recover evidence.
tsk_imageinfo -e /path/to/image.dd
FileAttrTable attrTable = db.openFileAttrTable();
attrTable.addRow(fileObj, "custom_key", "custom_value");
sqlite3 tsk_db.sqlite "SELECT * FROM examiner;"
sqlite3 tsk_db.db "SELECT name, extension FROM tsk_files WHERE extension = '.log';"
sqlite3 tsk_db.db "SELECT DISTINCT obj_type FROM tsk_objects WHERE obj_type IN ('Local Directory', 'Virtual Directory');"
usnjls -f /path/to/image.img
Summary
The Sleuth Kit is an open-source library and command-line toolkit for analyzing disk images and file systems, free to use, and run either directly from the command line or embedded as a library inside larger forensics tools. It works at the volume and file system layer across Microsoft and UNIX formats including NTFSNTFSThe default file system format for Windows, developed by Microsoft, storing files with rich metadata and access controls; cyber tools target it to parse artifacts like timestamps, alternate data streams, and the MFT., FAT, EXT2, and FFS, letting investigators recover and examine evidence gathered during incident response or from live systems. It is built for digital forensics practitioners, and its own documentation recommends pairing it with Autopsy, a graphical front end that automates image searching and integrity checks. First committed in 2008, it remains active with 171 contributors and 285 commits in the past year.
Open source forensic toolkit for analyzing Microsoft and UNIX file systems and disk images to identify and recover evidence.
How The Sleuth Kit helps
What files existed on this disk image before it was wiped or reformatted?
walks the file system layer directly, bypassing the operating system, to find and list entries the volume's own directory structures no longer point to
Which files were deleted, and can their original content still be recovered?
reads the file system's metadata structures for entries marked unallocated and pulls back the data blocks they still reference, when those blocks have not been overwritten
What happened on this machine, in what order, based on the timestamps left on its files?
extracts the modified, accessed, and created times recorded in file system metadata across the image so an investigator can lay out a timeline of activity
Is this disk image internally consistent with what a live system would report?
walks the same volume and file system structures a live OS would use, letting a second independent tool recreate and check the same results before they're relied on
Which partitions and file systems are actually present on a raw disk image, regardless of what the partition table claims?
inspects the volume layer itself, identifying the partitions and the file system type inside each one directly from disk structures
Can evidence gathered from this image be trusted to reflect what was really on disk, unmodified by the analysis itself?
operates read-only at the volume and file system layer and is open source, so the exact steps taken against the image can be inspected or rerun by a second party
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 The Sleuth Kit, 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 The Sleuth Kit 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
19 entries
No entries match these filters.
- April 20251
- March 20251
- August 20231
- January 20231
- August 20211
- March 20211
- September 20201
- May 20201
- January 20201
- October 20191
- August 20191
- April 20191
- January 20191
- October 20181
- August 20181
- May 20181
- February 20181
- October 20171
- August 20171
Project health
Issue, contributor and maintainer activity in sleuthkit/sleuthkit, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 10 +2 vs prior 12 months
- Maintainers 2 +1 joined · −3 left, last 12 months
- Bus factor 1 committers behind half the commits
- Community-filed 98% of issues opened, last 12 months
- Median time to close 118 days first maintainer reply 122 days
- Open backlog 441 of 739 issues ever filed
- Issues opened / month 3 · 0 communitymaintainers
- Open backlog 441
- Contributors / month 2
- Commits / month 4
- Stars 3,152
- features 2%
- other 98%
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.