apk-scanner.com
Wear Battery Notification
pl.example.bateria · Build 2.9.5
Analysis: complete. Static analysis completed for this build. A grade is not a guarantee of safety. Historical verification does not establish current reachability.
- Grade / score
- A · 98/100
- Finding categories
- 3
- Occurrences
- 4
- Scanned
- 2026-10-11T05:34:14.010Z
- Document issued
- 2026-10-14T11:14:56.125Z
- Historical verifications
- 0
Finding evidence
Open a category to review its occurrences. Printing includes all categories and occurrences.
Application data is backup-enabled · info · 1 occurrence
Backup is on by default on Android; this manifest states it explicitly. If the app stores sensitive local data, define dataExtractionRules/fullBackupContent to exclude it, or set android:allowBackup=false.
CWE-530 · CWE-312 · MASVS-STORAGE-1 · MASVS-STORAGE-2
android:allowBackup="true"
Google API key (client-shipped; restriction unverified) · low · 1 occurrence
Restrict the API key (application + API restrictions in Google Cloud Console); a client-shipped key is public, so restriction is the control.
CWE-798 · MASVS-STORAGE-1
AIza•••••••• (21–40 chars, redacted)
Firebase Storage bucket reference · low · 2 occurrences
Confirm the bucket/database denies anonymous read (enable auth / storage rules / RLS), then audit its contents for data already exposed while it was open.
CWE-200 · CWE-284 · MASVS-STORAGE-2
████████████████████████
Control coverage
Mapped static evidence does not establish a control pass. Manual assessment remains separate.
| Control | Requirement | Recorded status |
|---|---|---|
| MASVS-STORAGE-1 | The app securely stores sensitive data. | Review signal |
| MASVS-STORAGE-2 | The app prevents leakage of sensitive data. | Review signal |
| MASVS-CRYPTO-1 | The app employs current strong cryptography and uses it according to best practices. | No static findings · not a pass |
| MASVS-CRYPTO-2 | The app performs key management according to best practices. | No static findings · not a pass |
| MASVS-AUTH-1 | The app uses secure authentication and authorization protocols. | Manual assessment |
| MASVS-AUTH-2 | The app performs local authentication securely. | Manual assessment |
| MASVS-AUTH-3 | The app secures sensitive operations with additional authentication. | Manual assessment |
| MASVS-NETWORK-1 | The app secures all network traffic according to current best practices. | No static findings · not a pass |
| MASVS-NETWORK-2 | The app verifies the identity of the remote endpoint (e.g. certificate pinning). | No static findings · not a pass |
| MASVS-PLATFORM-1 | The app uses IPC mechanisms securely. | No static findings · not a pass |
| MASVS-PLATFORM-2 | The app uses WebViews securely. | No static findings · not a pass |
| MASVS-PLATFORM-3 | The app uses the user interface securely. | Manual assessment |
| MASVS-CODE-1 | The app requires an up-to-date platform version. | No static findings · not a pass |
| MASVS-CODE-2 | The app has a mechanism for enforcing updates. | Manual assessment |
| MASVS-CODE-3 | The app only uses software components without known vulnerabilities. | No static findings · not a pass |
| MASVS-CODE-4 | The app validates and sanitizes all untrusted inputs and follows secure-coding practice. | No static findings · not a pass |
| MASVS-RESILIENCE-1 | The app validates the integrity of the platform. | Manual assessment |
| MASVS-RESILIENCE-2 | The app implements anti-tampering mechanisms. | Manual assessment |
| MASVS-RESILIENCE-3 | The app implements anti-static-analysis mechanisms. | Manual assessment |
| MASVS-RESILIENCE-4 | The app implements anti-dynamic-analysis techniques. | Manual assessment |
| MASVS-PRIVACY-1 | The app minimizes access to sensitive data and resources. | No static findings · not a pass |
| MASVS-PRIVACY-2 | The app prevents identification of the user. | No static findings · not a pass |
| MASVS-PRIVACY-3 | The app is transparent about data collection and usage. | No static findings · not a pass |
| MASVS-PRIVACY-4 | The app offers user control over their data. | Manual assessment |
Build identity and signature
- Scan ID
- d62f933b-b780-48a7-9c23-cbdff9266640
- APK SHA-256
25f290670a0157385cfd2b9c9ee5cec2f7929d53c1a491e0530929692b251523- Capsule SHA-256
e58d468756dc1971ae6da0afe283dc6fa0c41723d4e21e2d375f3c1b5f7b1e5a- Signing key
- IE6LeZNX4dAAPLGr
Verify the signed JSON at apk-scanner.com/verify. This printed view is a presentation of the signed record; the JSON is the verification artifact.