# APK Inspection Reporter Offline APK evidence report without installing or executing Android code. Requires Python 3.10+ with Tkinter and Node 22+ on PATH. No pip/npm packages or other purchases. Run `python app.py`, load JSON containing an apk path, then inspect and choose a new JSON report. CLI: `python checker.py input.json new-report.json`. Use an absolute APK path or a path relative to this product folder in the native UI. Existing reports are refused. For an intentionally incomplete example run `python examples/make_sample.py`, then load examples/input.json. The synthetic file is not installable; it demonstrates missing-coverage warnings. Report contains APK SHA-256, byte budgets, manifest string candidates, DEX API-index references, provisional combination findings and explicit coverage/caveats. Manifest strings are not verified element declarations. Findings inherited from permission rules must be interpreted as candidate capabilities until declarations are checked. There is no malware/safe verdict or numerical probability. Corroboration cannot prove an API executes. Native libraries are counted but not inspected; signatures, resources, encrypted/downloaded payloads and runtime behavior are unexamined. Admission: 100MiB APK, 10000 entries, 128MiB declared expansion, 200:1 per-entry ratio, 4MiB manifest, 32MiB combined DEX. Duplicate/case collisions, unsafe paths, encryption, links and unsupported compression are refused. Selected entries have CRC and local headers checked; other payload bytes are not expanded or CRC-tested. Selected data is reserialized into a canonical temporary ZIP before the index parser runs. Node worker has a 30-second timeout and 256MiB JS heap limit (not a total RSS limit). Temporary files are removed. Parsing failures remain explicit unavailable coverage. Tests: `python -m unittest discover -s tests -v`. Automated structural and synthetic evidence tests do not certify arbitrary APK safety. Native visual acceptance pending.