apk-scanner.com
Hofstra Pride
com.sidearmsports.hofstra · Build 1.0.8
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
- B · 88/100
- Finding categories
- 8
- Occurrences
- 20
- Scanned
- 2026-10-07T03:59:00.316Z
- Document issued
- 2026-10-14T12:46:32.195Z
- 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"
Amazon S3 bucket reference · low · 9 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
https://████.amazonaws.com/███https://█████████████████.s3.amazonaws.com/███https://████.amazonaws.com/███https://████.amazonaws.com/███https://████.amazonaws.com/███https://████.amazonaws.com/███https://████.amazonaws.com/███https://████.amazonaws.com/███https://████.amazonaws.com/███
Private key material (third-party library artifact, shared across 35 unrelated developers) · low · 4 occurrences
Never ship private-key material in a client. Revoke/rotate the compromised key and hold it server-side or in a hardware-backed store.
CWE-321 · MASVS-CRYPTO-2
-----BEGIN PRIVATE KEY----- (redacted)-----BEGIN PRIVATE KEY----- (redacted)-----BEGIN PRIVATE KEY----- (redacted)-----BEGIN PRIVATE KEY----- (redacted)
Google API key (client-shipped; restriction unverified) · low · 2 occurrences
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)AIza•••••••• (21–40 chars, redacted)
Exported content provider without permission (third-party library artifact, shared across 9 unrelated developers) · low · 1 occurrence
Set android:exported=false, or require a signature-level android:permission, and scope grantUriPermissions narrowly.
CWE-926 · CWE-284 · MASVS-PLATFORM-1
TmxThirdPartyTicketContentProvider (exported, no permission)
Firebase Storage bucket reference · low · 1 occurrence
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
████████████
Sentry DSN · low · 1 occurrence
A client DSN is low-risk but confirm it is a client (not internal) DSN and cannot be abused to spoof events.
CWE-200 · MASVS-STORAGE-2
https://███████.ingest.us.sentry.io/███
Cleartext (HTTP) traffic permitted · medium · 1 occurrence
Set android:usesCleartextTraffic=false and/or a networkSecurityConfig that forbids cleartext; serve all endpoints over HTTPS.
CWE-319 · MASVS-NETWORK-1
android:usesCleartextTraffic="true"
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. | Review signal |
| 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. | Review signal |
| 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. | Review signal |
| 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
- 2209232e-e655-42d3-bac3-7abe00635bd0
- APK SHA-256
d986ef2edef53561461d1c9baed3c9c0d9f0ead87150c256c17c6a728bbbde32- Capsule SHA-256
6a5ceafe0a7579d05ae38ddca364c795135890fa69f7a660e1e060d524ab0010- 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.