Open Source

We build on open-source forensics and give back.

Most of what we can read from a phone, we can read because the community wrote a parser and shared it. We use these tools, check our results against them, and contribute what we learn.

Tools we use and recommend

Independent projects with their own maintainers. We list them because we rely on them, and because each dataset names the parser that reads each file. Listing does not mean the projects endorse us, or that we speak for them.

Our contributions

Every merged pull request and every one that has a post, with the issue it addresses, the method and the value. Each post links the pull request itself.

ALEAPP (Android)

Android parsers and bug report readers.

iLEAPP (iOS)

iOS parsers for file system, unified log and sysdiagnose artifacts.

sysdiagnose framework (iOS)

The same iOS 27 parser, offered to the EC-DIGIT-CSIRC framework.

How we contribute back

The same steps every time, so maintainers know what to expect.

  1. Study and write up

    We find out how a device records something, publish the method and the limits, and cite the evidence.

  2. Make a synthetic fixture

    We build a small test file in the real layout with invented values and known answers. Never case data, never real identifiers.

  3. Write the parser and tests

    The parser comes with tests that read the fixture and check the answers, in the style of the project.

  4. Talk to the maintainers

    We open an issue first, follow the project's contribution guide, and accept their review.

  5. Match the licence

    Contributions carry the upstream licence. We keep nothing back.

Contribution principle

What we learn about how devices record their history belongs to everyone who has to read it. We publish it, and we put the parsers where examiners already look.

On GitHub

Counts read from GitHub on 5 November 2026.

  • 26Merged pull requests (ALEAPP and iLEAPP)
  • 4In review
  • 30Posts