How abrignoni/ileapp works
Project type and purpose
• This is an open-source forensic analysis tool (iLEAPP) written in Python.
• It provides both a CLI (ileapp.py) and a GUI (ileappGUI.py) for parsing iOS/iPadOS logs, events, plists, and generating reports (HTML, TSV, LAVA, timeline, optional KML).
• It is extensible via a plugin architecture: each artifact extractor lives as a Python module in scripts/artifacts/.
High-level file-structure analysis
• Top-level:
• ileapp.py (CLI entry point)
• ileappGUI.py (tkinter-based GUI entry point)
• requirements.txt (Python dependencies)
• .github/workflows/… (CI jobs: updating module info, generating filepath search summaries)
• whl_files/… (binary wheels Python components depend on)
• scripts/: core engine and helpers
• plugin_loader.py (discovers & loads artifacts from scripts/artifacts/)
• ilapfuncs.py, artifact_report.py (utilities for parsing & report generation)
• filetype.py, search_files.py, tz_offset.py, etc.
• ccl/, keychain/, ktx/ (sub-libraries for decompression/file formats)
• filetypes/ (file-mimetype classification)
• pyinstaller/ (spec files for building standalone executables)
• scripts/artifacts/: ~400 modules, each defines a __artifacts_v2__ metadata dict and a processing function.
• admin/: developer docs, data lists, module-info scripts, test cases, test result artifacts.
README insights
• Describes supported iOS versions, usage (CLI vs GUI), build steps (pyinstaller), plugin metadata format, and test guidelines.
• Emphasizes dynamic loading of artifact modules via a __artifacts_v2__ API.
Main components & relationships
A. Frontends
– CLI (ileapp.py)
– GUI (ileappGUI.py using tkinter + embedded webview)
B. Core “engine”
1. FileSeeker abstraction (handles zip, tar, FS, backup folders)
2. PluginLoader (loads every Python file in scripts/artifacts/)
3. Artifact processor functions (one per artifact module)
4. Utility layers:
• ilapfuncs.py (common parsing helpers)
• artifact_report.py (HTML/TSV/LAVA/timeline output)
• filetype.py, parse3.py, chat_rendering.py, etc.
5. Report output directory (HTML, data files, timeline JSON, optional KML)
C. Packaging
– PyInstaller spec files to produce Windows .exe and macOS .app executables
D. Testing & Admin
– admin/test/ (JSON test definitions + sample zipped input files)
– admin/scripts/ (scripts to generate module info, filepath summaries)
– CI workflows (.github/workflows) depend on those admin scripts
Architectural patterns & design principles
• Plugin-based, dynamic loading: loose coupling between core engine and artifact modules
• Layered architecture:
1. Presentation (CLI / GUI)
2. Application core (FileSeeker, PluginLoader)
3. Domain (artifact processors)
4. Infrastructure (file I/O, compression libraries, external dependencies)
5. Reporting (HTML, TSV, LAVA, timeline)
• Single responsibility: each artifact module handles exactly one data-extraction concern