Open-source project
sleuthkit/autopsy avatar
sleuthkit/autopsy

Autopsy's readme is README.txt, dated 2016, and its bundled components carry four licenses

Autopsy® is a digital forensics platform and graphical interface to The Sleuth Kit® and other digital forensics tools. It can be used by law enforcement, military, and corporate examiners to investigate what happened on a computer. You can even use it to recover photos from your camera's memory card.

3,451 stars717 forksJavaLicense varies

At a glance

What is it?
A Java desktop front end to The Sleuth Kit for digital forensics, on the Apache 2.0 licence, developed on a develop branch and released as autopsy-prefixed tags. The readme is a plain text file dated March 2016 that still claims to have run on XP and Vista, the component list mixes Apache, LGPL, GPL and public domain terms, and the embedded resources list ends mid-entry.
Who is it for?
Autopsy is the tool to use when you need a graphical workbench rather than command line output, because the parsing, carving and search engines underneath are The Sleuth Kit and a set of established open source components, and the value Autopsy adds is the case-oriented interface on top of them, including multi-user collaboration on one case. Three things to check before you rely on it.
Can I use it commercially?
Not without permission. GitHub finds no licence file in the repository, and without a licence all rights are reserved by default: you may read the code but not reuse it. Check the README, or ask the authors, before using it.
Is it still maintained?
Yes. The repository last received commits 148 days ago.
What is it written in?
Mainly Java, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • sleuthkit/autopsy3,451 ★ · +102
Star history
Repository2026-09-242026-11-15
sleuthkit/autopsy3.3k3.5k

102 Stars in the last 52 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

The readme is a text file dated March 2016

The documentation at the root of this repository is README.txt, not a Markdown file, and the first three lines are a title, a URL and the date March 15, 2016. Everything after that describes a program ten major versions behind the one being released: the current tags are autopsy-4.22.1, 4.23.0 and 4.23.1, with the newest published in May 2026. The readme's own platform claims match its date. It says the software was designed to be cross-platform across Windows, Linux and MacOSX, that the current version is fully functional and fully tested only on Windows, and that it has been run on XP, Vista and Windows 7 with no problems. The embedded component list does reflect recent work, naming a Java 17 runtime and the NetBeans 15 platform, so the file has been edited since 2016 without its framing being updated.

The licence field is unrecognised while the text says Apache 2.0

Three sources describe the licence and one of them is empty. The repository's licence metadata comes through as unknown, while the readme states twice that Autopsy 4 is released under the Apache 2.0 licence, and the tree contains a file named LICENSE-2.0.txt that the text points to for details. The substantive answer is not in doubt, since a named licence file exists and the readme is consistent with it, but a tool that reads only the metadata field will show nothing at all, and that is the field automated compliance checks usually read. The readme also adds a caveat in the same paragraph, noting that some libraries Autopsy uses may have different but similar open source licences, which is the opening of the next section's problem.

The bundled components carry four different licences

The embedded software section is a long list with a licence link per entry, and the licences are not uniform. Most sit under Apache 2.0, including Solr with Lucene and TIKA for keyword search, Metadata Extractor for Exif data and the NetBeans platform. Libewf, zlib, GStreamer, Jericho and the 7Zip bindings are listed under LGPL terms. Regripper, which pulls recent activity, is under GPL. Reflections, used for ingest module loading, is listed under a public domain style licence. Regripper is the one to note, because GPL inside an Apache 2.0 product is a different kind of obligation than the LGPL and public domain entries, and the readme's phrasing, different but similar, does not address the difference. The list of tools is also where you learn what the software actually does: E01 file support, keyword search, video viewing, Exif extraction and image carving.

Tags carry a project prefix and development happens on develop

The release tags are named autopsy-4.23.1 rather than 4.23.1, and the default branch is develop, not master or main. Together those two facts decide how you automate against this repository. A tag watcher or release script that assumes semantic version tags will match nothing, and a clone of the default branch gives you the development line rather than the last release. The release history itself is steady rather than bursty, with 4.22.1 in April 2025 followed by 4.23.0 and 4.23.1 a year apart in April and May 2026. The most recent push to the develop branch is dated 2026-06-20, so the branch is ahead of the newest tag by a couple of months. The metadata itself is not marked as archived.

The Sleuth Kit version is pinned by a script rather than a submodule entry

Autopsy is a front end, so the version of the toolkit underneath determines what it can parse, and this repository handles that with a script at the root named setupSleuthkitBranch.py alongside a TSKVersion.xml file. That pairing says the dependency is tracked by branching and a version declaration rather than by a package manager. The build follows the same older school: Ant build files for Windows and for Unix, an Ivy configuration for dependency resolution, a NetBeans project directory and a bundled platform directory. Continuous integration is configured twice over as well, with both a Travis configuration and an AppVeyor configuration at the root, alongside GitHub workflow directories. Nothing in the tree suggests which of those three is authoritative now.

Bundled Python modules and an experimental module directory

Two directories tell you something about the shape of the software. One is named InternalPythonModules, which means Python modules ship inside the application rather than being resolved from an interpreter environment, the usual arrangement for a tool that has to run identically on an examiner's machine without asking them to install anything. The other is named Experimental, a module category kept separate from the rest, which tells you the module system is designed to let new analysis code be added without being part of the supported surface. Alongside them are pythonExamples, a Thunderbird parser, a Scalpel file carver, a recent activity module, a keyword search module and an image gallery. A file named git-daemon-export-okay sits at the root, which is the marker web hosting tools look for, an odd artefact for a forensics application.

The embedded resources list ends on an icon set with no licence line

After the software components, the readme has a second list for other resources such as icons, and it is shorter and less complete. Four sets are named: Silk icons version 1.3, Fugue icons version 3.5.6, WebHostingHub Glyphs and a set described only as free as in free. The first three each carry a Creative Commons attribution 3.0 link. The fourth entry stops after its name, with no web page and no licence line, so the list is unfinished. Both of the third-party icon sets named are long-retired collections, which is worth knowing if you are redistributing: attribution licences attach to the artwork itself, and Autopsy's Apache 2.0 grant does not cover them.

Editorial conclusion

Autopsy is the tool to use when you need a graphical workbench rather than command line output, because the parsing, carving and search engines underneath are The Sleuth Kit and a set of established open source components, and the value Autopsy adds is the case-oriented interface on top of them, including multi-user collaboration on one case. Three things to check before you rely on it. Windows is the only platform described as fully functional and fully tested, and the platform notes in the documentation are ten years old, so plan for Windows. The component licences are not all the same as the project's, which matters if you redistribute anything built with it. And the release tags are prefixed with the project name rather than being plain semantic versions, so anything that watches tags needs to be told how to match them.

Frequently asked questions

how to use autopsy software

Autopsy is a graphical front end to The Sleuth Kit and other open source forensics tools, so the work happens through its case interface rather than a command line. Documentation support is a built-in help system plus a QuickStart Guide that ships with the installer.

how to install autopsy on mac

The software is designed to run on Windows, Linux and MacOSX, and the tree carries a document about running it on Linux and macOS along with a Unix setup script. It is described as fully functional and fully tested only on Windows.

What licence is Autopsy released under?

The Apache License version 2, with the terms in a file named LICENSE-2.0.txt at the repository root. Note that several bundled third-party components carry their own licences, including LGPL, GPL and public domain terms.

Which third-party tools does Autopsy bundle?

Among them The Sleuth Kit for disk images, Libewf and zlib for E01 files, Solr with Lucene and TIKA for keyword search, GStreamer for video, Regripper for recent activity, Pasco2 for Internet Explorer activity, Jericho for HTML extraction, Metadata Extractor for Exif data and Scalpel for file carving.

Does Autopsy have a localized version?

A Japanese localized version is described, and it requires the Microsoft Japanese language pack to be installed and the default locale set to Japanese before it will run.

Official sources

  1. Issues
  2. Project website
  3. README
  4. Releases
  5. sleuthkit/autopsy on GitHub
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/sleuthkit-autopsy.svg)](https://hysenlabs.com/projects/sleuthkit-autopsy)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/sleuthkit-autopsy.svg)](https://hysenlabs.com/projects/sleuthkit-autopsy)

Was this useful?