APK File Verification Policy
How MiniMilitiaAPK.cc should record file identity, checksums, signing certificates, permissions, scan evidence and device tests before enabling a download.
Every File Needs a Reproducible Evidence Record
This policy defines the minimum checks required before an APK download can be enabled on the site.
A filename, version label or antivirus badge is not enough to verify an Android package.
The exact file must have recorded metadata, a checksum, certificate details, permissions and named-device test results.
Official facts and third-party MOD claims must be labelled separately.
If evidence is missing or contradictory, the file remains unpublished or is removed.
Identity Checks
Record filename, size, package name, version name and version code.
Security Review
Calculate SHA-256, inspect the certificate and review manifest permissions.
Functional Tests
Document install, launch, stability and feature results on named devices.
APK Verification Workflow
Apply the same workflow to every new file and to every replacement file, even when the visible version number is unchanged.
Required Steps
All test results must refer to the same binary represented by the published checksum.
A matching checksum proves file identity, not safety; it must be combined with source, certificate, permission and behaviour review.
Publication Criteria and Rejection Triggers
Publish Only When
Reject or Remove When
Verification Policy Summary
This policy is designed to make file decisions transparent, repeatable and easy for users to understand.
No download action should be enabled while critical identity or test fields remain pending.
When a file changes, create a new evidence record rather than silently reusing the old checksum or results.