Before an Android release
Available · Build evidence
Review the coverage report, manifest findings, signer configuration and packaging checks. Verify the signed artifact and test your actual device and delivery setup.
Use cases
For the people
who ship the application.
Focused tools for concrete security decisions. Start with supported Android workflows today; help shape what comes next.
Inside an Android app
Available · Runtime engine
Evaluate supported dependency-call protection and threat checks before choosing a response policy. Keep unavailable evidence separate from a confirmed threat or a clean result.
In a delivery pipeline
Available · Structured reports
Use the Android engine’s JSON, HTML and SARIF outputs in compatible tools. A successful build establishes required packaging checks, not immunity from runtime attacks.
Across the wider application
Planned · Product direction
Connect platform-specific client evidence with backend verification, policy and self-hosted operations. This is the family’s direction, not a shipped cross-platform service.