The LEAPP family (ALEAPP, iLEAPP, RLEAPP, VLEAPP): open-source artefact parsing
What the LEAPP parsers are, how they fit with Autopsy and commercial suites, what is publicly known about their validation, and how to contribute.
Updated
In short
The LEAPPs are open-source Python parsers that turn data you already hold, such as a device extraction or a provider return, into reports; they do not acquire data from a device. Public validation evidence is thin: the DFRWS 2020 talk is a statement of purpose, the iLEAPP README describes per-module test fixtures that continuous integration checks, and the one independent item cited, a small preprint that has not been peer reviewed, found that, in synthetic test databases, three schema changes made ALEAPP's WhatsApp parsers give incomplete output and a fourth change, to timestamp representation, produced timestamp errors, with no visible warning in any of those four materially wrong runs. SWGDE 18-Q-001-2.1 says testing is not necessarily pass or fail, since some faults limit how a tool is used rather than whether, and SWGDE 18-F-003-2.0 notes that a second forensic tool can corroborate results or provide additional data.
What they are
The LEAPPs are open-source Python parsers maintained by Alexis Brignoni and contributors. Each takes data you already hold (a device extraction or, for RLEAPP, a provider return) and turns the artefacts inside it into reports. They do not acquire data from a device; acquisition comes first (see acquisition types). According to the project site, leapps.org, the suite now includes eight tools. The four covered here are:
- iLEAPP, the iOS Logs, Events, And Plists Parser. Its README says it parses iOS and iPadOS extractions into HTML, TSV, timeline, KML and LAVA output, and supports iOS and iPadOS 11 through current versions.
- ALEAPP, the Android Logs Events And Protobuf Parser, for databases, logs and application data from Android extractions (ALEAPP repository).
- RLEAPP, described on leapps.org as parsing "ISP returns": user-generated data stores and provider-supplied data from social media sites. The RLEAPP README uses Snapchat returns as its worked example.
- VLEAPP, for vehicle infotainment and telematics data from connected-car systems and IVI units, per leapps.org (VLEAPP repository).
The expansions of the RLEAPP and VLEAPP acronyms differ between the project site and the repositories' own descriptions, so use the abbreviations. As of the GitHub API on 2026-10-29, all four repositories are MIT-licensed, were pushed to within the last two days, and have releases dated 2026-10-24 (iLEAPP v2026.4.5; the other three v2026.4.4). The READMEs describe prebuilt Windows, macOS and Linux releases that need no Python install, plus a GUI and a command line. iLEAPP accepts folders, ZIP, TAR and GZIP archives, single files and iTunes/Finder backups, including encrypted ones.
How they fit with other tools
Alongside commercial suites. A typical workflow uses a commercial or other tool to acquire, then points a LEAPP at the resulting archive. SWGDE 18-F-003-2.0 (version 2.0, 2025-08-21) notes that a single tool may not extract or present all data contained in a mobile device and that using a second forensic tool can corroborate the results or provide additional data. A free parser run against the same extraction is one inexpensive way to apply that principle to the analysis stage, though it does not independently check the acquisition itself.
Inside Autopsy. Autopsy ships ingest modules that run the parsers for you. Per the Autopsy 4.23.0 documentation, the iOS Analyzer module runs iLEAPP and converts the results into Autopsy results, operating on .tar or .zip files found in a logical-files data source or disk image, with output under Results, Extracted Content. The Android Analyzer does the same with ALEAPP. See the Autopsy tool page.
Validation: what is and is not public
Brignoni presented the frameworks at DFRWS USA 2020 in a talk titled "iLEAPP & ALEAPP: Parse and validate mobile forensic artifacts with Python". The abstract says the need to test and validate new artefacts has accelerated because nearly every case involves a phone or tablet, and presents the tools as an open-source answer. That is a statement of purpose, not a validation report.
The project's own quality process is visible in the iLEAPP README: a contributed module should arrive with a small test fixture cut from a real extraction and recorded expected output (sample_data), and the repository's continuous integration compares a module's output with those expectations. This is regression testing for each parser, run by the maintainers. It does not replace a laboratory's own validation.
Independent literature is thin. The one independent item cited here is a preprint that its host states "has not been peer reviewed". It tested ALEAPP's WhatsApp contacts and one-to-one message parsers against synthetic SQLite databases with known contents under five conditions of schema change. Three conditions produced incomplete extraction, totalling 45 missed artefacts; one produced five timestamp errors; no false positives were seen; and none of the four materially wrong runs gave the examiner any visible warning. This is a small study on two artefacts and one tool version, but it illustrates the general risk with any parser: when an app updates its database layout, output can be silently incomplete.
What follows for practice:
- Record the tool version and the date, and keep the full output folder.
- Verify important artefacts against the raw database in an SQLite viewer, especially for messaging apps that update often.
- Test against known data before relying on a module. SWGDE 18-Q-001 lists commercial, open-source and custom tools as sources of forensic tools and says testing is not necessarily pass or fail: some faults limit how a tool is used rather than whether.
- Where a result matters, cross-check it with a second tool. See choosing a mobile forensics tool.
Contributing
The iLEAPP README states that artefact modules live in scripts/artifacts/ and load dynamically at run time, and points new authors to a step-by-step "How to Write an iLEAPP Module" guide on leapps.org, plus documentation on the artefact info block, helper functions, LAVA output and testing. For a pull request that adds or changes an artefact, it asks for a fixture under 10 MB (10 to 25 MB attached to a PR comment; larger ones arranged with a maintainer) and generated sample_data, and it sets one firm rule: whatever you commit becomes public, so use only data you are allowed to share, such as a test device you populated yourself or a public research image, and never casework. The ALEAPP README invites contributors to contact the maintainer, and leapps.org lists contributor, translator and mailing-list pages.
For tool-level notes and support details, see the pages for iLEAPP, ALEAPP, RLEAPP and VLEAPP.
Sources
- LEAPPs: Digital Forensics Tools (project site)
- abrignoni/iLEAPP on GitHub
- abrignoni/ALEAPP on GitHub
- abrignoni/RLEAPP on GitHub
- abrignoni/VLEAPP on GitHub
- Autopsy 4.23.0 user documentation, iOS Analyzer (iLEAPP)
- Autopsy 4.23.0 user documentation, Android Analyzer (aLEAPP)
- Brignoni, iLEAPP & ALEAPP: Parse and validate mobile forensic artifacts with Python (DFRWS USA 2020)
- Bulla, Failure Transparency in Android Forensic Parsing Under Schema and Representation Drift: A Controlled ALEAPP Microbenchmark (preprint, not peer reviewed)
- SWGDE 18-F-003-2.0, Best Practices for Mobile Device Evidence Collection & Preservation Handling and Acquisition (Version 2.0, 2025-08-21)
- SWGDE 18-Q-001-2.1, Minimum Requirements for Testing Tools Used in Digital and Multimedia Forensics (2024-03-07)