What was actually supplied?
The initial evidence review covered 21 website pages and 25 picture files. It supplied 0 APK binaries. A page claim or an illustration cannot substitute for a specific installer and a traceable publisher record.
Nine fields for a release record
| Field | Required representation |
|---|---|
| Publisher | Traceable name and publisher-controlled evidence URL. |
| Package identity | Exact Android application ID. |
| Version | versionName plus integer versionCode. |
| Release date | Publisher release date in YYYY-MM-DD form. |
| Download URL | Approved HTTPS destination for this package. |
| File | Exact byte count and file SHA-256. |
| Signing identity | Certificate SHA-256 and any documented key lineage. |
| Compatibility | Integer minimum API and supported ABIs. |
| Verification record | UTC check timestamp, reviewer and method/source record. |
Reproducible file checks
Use a cryptographic hash of the actual APK to identify its bytes. Android SDK tools can inspect the package manifest and signature. Preserve their complete outputs privately alongside the publisher source and review record.
sha256sum app.apk
apksigner verify --verbose --print-certs app.apk
apkanalyzer manifest application-id app.apk
apkanalyzer manifest version-name app.apk
apkanalyzer manifest version-code app.apk
apkanalyzer manifest min-sdk app.apkPassing a signature check establishes a technical signing property. Compare the certificate or valid lineage with a trusted publisher record; it is a separate step from a malware assessment.
What the record does not certify
An integrity match does not certify gameplay fairness, privacy behaviour, legal classification or payment reliability. A full assessment would identify its own scope, tools, versions, test conditions and findings. Our current record is a website/content review, with 0 device-based APK tests.
Guide date and release date are separate
The 26 October 2026 date records this substantial website revision. It is not a promised daily check or an app release date. When an installer changes, verify its record and rebuild the relevant pages instead of updating only a date label.
App details and evidence record
Numbers below describe this guide, its examples and available evidence. Release-specific version, file size, minimum API and signing fields require the actual publisher-linked installer.
| Parameter | Value and scope |
|---|---|
| Guide revision | 2026-10-26 |
| Source references | 2 linked below |
| Input HTML pages | 21 |
| Input picture files | 25 |
| Input APK binaries | 0 |
| Release-record field groups | 9 |
| SHA-256 representation | 256 bits · 64 hex characters |
| Publisher-linked APK files inspected | 0 · publisher release review pending |
Method: release evidence requirements · Editorial responsibility: TP-Mst.
Sources & scope
- Android Developers: APK signature verification
- Android Developers: app distribution and installation permissions
References reviewed for this guide on 26 October 2026. Original examples and calculations are identified in context. A document review is separate from a device-based APK test.