RLEAPP
Open sourceActive
Despite sharing the LEAPP family name, RLEAPP targets provider returns rather than mobile devices. The GitHub description expands the name as 'Returns Logs Events And Properties Parser'; the README title says 'Protobuf'. Latest release v2026.4.5 (2026-11-03); on 2026-11-10 main was 49 commits ahead of it. The README text cited here is the same at v2026.4.5 as on main apart from an added Licence section on main.
RLEAPP is an open-source LEAPP-family parser from Alexis Brignoni and contributors for ISP and service-provider warrant returns such as those from Google, Meta and Snap. It is not a device parser: it reads the data a provider returned, not a phone extraction. It outputs HTML, TSV, timeline, KML and LAVA reports and ships GUI/CLI builds for Windows, macOS and Linux.
Facts
| Website | github.com |
|---|---|
| Vendor | Alexis Brignoni and contributors |
| Licence | Open source (MIT) |
| Category | Artefact parsers |
| Functions | Parsing, Reporting |
| Targets | Cloud services |
| Runs on | Windows, macOS, Linux |
| Pricing | Free |
| Users | Law enforcement, Research, Open-source DFIR community |
| Last activity | 2026-11-07 · Latest commit on main (2026-11-07); latest release v2026.4.5 published 2026-11-03 [github.com] |
| GitHub activity | abrignoni/RLEAPP · 152 stars · last push 2026-11-07 · latest release v2026.4.5 (2026-11-03) · checked 2026-11-10 |
Capabilities
- Parses ISP/provider warrant returns (Google, Meta, Snap and more), according to the LEAPPs project index. [leapps.org]
- CLI input types are zip, tar, fs, gz and raw; raw reads disk images and forensic containers in place, without mounting or administrator rights. [github.com]
- Five Snapchat artifacts (snapAiConvN, snapConvN, snapMemN, snapRepconN, snapStoryN) match a return's media files to its CSV rows by file name. [github.com]
- Pre-built GUI/CLI releases exist for Windows (x64/ARM), macOS (arm64/x64) and Linux (x64/ARM) with a SHA256SUMS file. [github.com]
Limitations
- The README says the raw input is for an image that holds a return, not for an image of a whole computer or phone. [github.com]
- The five Snapchat artifacts ask for every path containing a dot; on a public 256 GB Windows 11 test image the README computes that this matches 107 GB, so those artifacts should be left out when reading a return from a whole-disk image. [github.com]
Links
Related tools
Guides that discuss this tool
- 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.
- Cloud extraction: tokens, backups and legal process · Three routes to phone data in the cloud: provider legal process, credential or token tools, and account-holder export, with Apple, Google and SWGDE sources.
Sources
- RLEAPP repository and README (github.com)
- LEAPPs project index (leapps.org/llms.txt) (leapps.org)
- RLEAPP releases (github.com)
- RLEAPP README at v2026.4.5 (github.com)
- GitHub: abrignoni/RLEAPP commits (github.com)
Reviewed . Spotted an error? See the corrections policy.