magicrescue
1.1.8 open-sourceThe section your link pointed to isn't on magicrescue's page any more, so we've brought you to the top.
Scans block devices for recognizable file types using magic bytes and extracts them, functioning as an undelete and drive recovery utility.
magicrescue -r mbox disk_image.raw magicrescue -r mbox-mozilla-inbox disk_image.raw magicrescue -r recipes/gimp-xcf <image_file> magicrescue -b -x ext4 -x ntfs magicrescue -b /dev/sda1 magicrescue magicrescue -d recovered/ -r gzip /dev/sda1 magicrescue -d recovered/ -r mp3-id3 /dev/sda1
Summary
magicrescue is an open-source command-line utility that scans a block device for known file types by matching magic bytes and hands each match to an external program for extraction, working as both an undelete tool and a recovery aid for corrupted drives or partitions. It suits DFIRDFIRDigital forensics and incident response, investigating what happened during a security incident and containing it. The work includes preserving evidence, reconstructing activity and restoring systems. practitioners and system administrators handling disk recovery or forensic carving tasks, rather than anyone needing a polished GUIGUIA graphical user interface, controls such as windows, buttons and menus. It lets people use software visually rather than entering commands.. It runs directly against raw devices on any UNIXish system with no dependencies beyond a C library, though its own README warns it should only be run in a sandboxed environment given the unsafe languages and arbitrary disk data involved. First committed in 2018 with three contributors, the project carries a formal deprecation notice from its author and has seen no commits in the past year, so it should be treated as a stable but unmaintained tool.
Scans block devices for recognizable file types using magic bytes and extracts them, functioning as an undelete and drive recovery utility.
How magicrescue helps
Which deleted files can still be pulled off a drive after the filesystem has forgotten about them?
scans the raw block device for known magic byte signatures and hands each match to an external extraction program, independent of what the filesystem's directory entries say
Can a corrupted or unmountable partition still yield usable files?
reads magic bytes directly off the block device rather than through the filesystem, so files come back as long as their data is still physically present
What file types can be recovered from this disk right now?
matches disk contents against a set of known magic byte signatures and only acts on the types it recognizes, so the answer is bounded by which signatures are defined
Which parts of a large disk actually contain recoverable data worth extracting?
walks the raw device sequentially checking for signature matches, turning an entire block device into a set of located, extractable files rather than a wall of undifferentiated bytes
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 magicrescue, 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 magicrescue 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.
- November 20092
- February 20091
- January 20081
- July 20041
- May 20043
- April 20046
- March 20045
Project health
Issue, contributor and maintainer activity in jbj/magicrescue, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 0 ±0 vs prior 12 months
- Maintainers 0 +0 joined · −0 left, last 12 months
- Bus factor 0 committers behind half the commits
- Community-filed not measured of issues opened, last 12 months
- Median time to close not measured issues closed, last 12 months
- Open backlog 1 of 3 issues ever filed
- Issues opened / month 0 · 0 communitymaintainers
- Open backlog 1
- Contributors / month 0
- Commits / month 0
- Stars 11
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.