Dissect
3.22 open-sourceThe section your link pointed to isn't on Dissect's page any more, so we've brought you to the top.
Digital forensics and incident responseDigital forensics and incident responseDigital forensics and incident response, investigating what happened during a security incident and containing it. The work includes preserving evidence, reconstructing activity and restoring systems. framework for parsing and analysing forensic artefacts from disk images, filesystems, and containers.
target-query --direct single_file.bin acquire --children --enable-nfs <host_or_ip> target-shell >>> reload() dissect target-diff /path/to/image1 /path/to/image2 dissect -f os.windows.regf.cam /path/to/target target-yara <rules> <targets> target-fs ls -lh <path> dissect.target-query -f '*filesystem*' --dry-run /path/to/disk.dd dissect.target-query -xf '*registry*' -f '*/etc/*' /path/to/disk.dd dissect.target-shell /path/to/vm.ova registry
Summary
Dissect is an open-source digital forensics and incident response framework that extracts and parses forensic artefacts directly from disk images, VM containers and other sources, without first mounting or manually reconstructing filesystems. It is run through command-line tools like target-query and target-shell, or installed as a Python library via pip, and it works across containers such as E01E01A forensic disk image format that stores a drive's contents in segmented files with built-in checksums and metadata, widely used in digital forensics because it supports compression and chain-of-custody verification., VMDK and QCoW, filesystems 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. and ExtFS, and operating systems from Windows to ESXi. It is aimed at incident responders and forensic investigators who need to pull artefacts like registry keys, event logs and prefetch files from many hosts at once rather than one image at a time. Developed by Fox-IT (NCC Group), the project dates to 2022 and has had 11 contributors and 13 releases in the tracked window, though its most recent release was around six months ago.
Digital forensics and incident response framework for parsing and analysing forensic artefacts from disk images, filesystems, and containers.
How Dissect helps
Which user accounts exist on a disk image without mounting it first?
queries the parsed filesystem and registry directly from the container and lists every account it finds, from built-in service accounts to local users
What actually happened on a compromised host, across its registry, logs and prefetch, without extracting each artefact by hand?
reads runkeys, event logs and prefetch straight from the source container in one pass and returns them in a common, queryable form
Can I build one timeline of events across every host in this investigation, not just one image at a time?
runs the same artefact query across many targets at once and returns results in a shared format that can be merged into a single timeline
Is this ransomware-encrypted virtual disk still readable for investigation?
parses the disk structure and filesystem directly from the VM container, so artefacts can be pulled out even when the guest OS itself would refuse to boot
Which of these thousands of hosts show the indicator I'm hunting for?
runs the same query or check against each target in bulk and reports matches back per host, turning a host-by-host search into a single pass
How do I pull a forensic copy off a live VM on a hypervisor without shutting it down or fighting file locks?
creates a lightweight container of the running machine directly from the hypervisor, sidestepping locked files and avoiding any downtime
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 Dissect, 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 Dissect 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
22 entries
No entries match these filters.
- February 20261
- November 20251
- September 20251
- May 20251
- March 20251
- December 20241
- November 20241
- September 20242
- July 20241
- May 20241
- March 20241
- January 20241
- December 20231
- November 20231
- September 20231
- August 20232
- July 20231
- May 20231
- March 20231
- February 20231
Project health
Issue, contributor and maintainer activity in fox-it/dissect, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 3 −3 vs prior 12 months
- Maintainers 0 +0 joined · −2 left, last 12 months
- Bus factor 0 committers behind half the commits
- Community-filed 36% of issues opened, last 12 months
- Median time to close 52 days first maintainer reply 9.2 days
- Open backlog 10 of 34 issues ever filed
- Issues opened / month 0 · 1 communitymaintainers
- Open backlog 10
- Contributors / month 0
- Commits / month 0
- Stars 1,156
- bugs 9%
- features 18%
- other 73%
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.