Brave Beta
Brave Software · Build 1.98.52
Static checks identify review items, not a guarantee of safety.
Overview
3 finding categories to review
Brave Beta (com.brave.browser_beta) scored grade A, 97 out of 100, in a static scan of version 1.98.52 on 2026-10-09. It has no high or critical findings, and 3 lower-severity finding categories across 5 occurrences. No tracking SDKs were recognised in the package. This is static analysis of a single build: it does not observe the app running and does not establish that any data is exposed.
Start with these findings
lowExported content provider with path-restricted permissions (third-party library artifact, shared across 8 unrelated developers)2 occurrences
Interpretation & review guidance
An exported content provider declares no permission. Other apps on the device may reach it — verify it enforces access control internally; this flags the attack surface, not a confirmed leak.
- Evidence
- 2 recorded occurrences in the analyzed APK. These are distinct stored findings, not a count of every source match.
- Verification
- Static detection; current reachability is not established.
lowFirebase Storage bucket reference2 occurrences
Interpretation & review guidance
A Firebase Cloud Storage bucket reference (the default <project>.appspot.com). Storing user files here is normal — it's only an exposure if the Storage security rules allow public read/list, which live verification tests.
- Evidence
- 2 recorded occurrences in the analyzed APK. These are distinct stored findings, not a count of every source match.
- Verification
- Static detection; current reachability is not established.
lowGoogle API key (client-shipped; restriction unverified)1 occurrence
Interpretation & review guidance
Android apps are designed to ship Google API keys in the client; Google restricts them by app signing certificate + enabled API. This is only a problem if the key is left unrestricted — presence alone is expected, not an exposure.
- Evidence
- 1 recorded occurrence in the analyzed APK. These are distinct stored findings, not a count of every source match.
- Verification
- Static detection; current reachability is not established.
Build & components
0 components recorded. Certificate parsing does not validate APK signature integrity.
Inspect build evidence →Findings
3 categories · 5 occurrences. Severity totals describe categories. Expand a finding for interpretation and review guidance.
lowExported content provider with path-restricted permissions (third-party library artifact, shared across 8 unrelated developers)2 occurrences
Interpretation & review guidance
An exported content provider declares no permission. Other apps on the device may reach it — verify it enforces access control internally; this flags the attack surface, not a confirmed leak.
- Evidence
- 2 recorded occurrences in the analyzed APK. These are distinct stored findings, not a count of every source match.
- Verification
- Static detection; current reachability is not established.
Evidence preview
- Evidence type
- Parsed app configuration
- Representative location
AndroidManifest.xml:um.chrome.browser.provider.ChromeBrowserProvider- Recorded match
ChromeBrowserProvider (exported, some paths guarded)- Detector rule
manifest- Recorded file locations
AndroidManifest.xml:um.chrome.browser.provider.ChromeBrowserProvider
2 recorded findings have inspectable metadata. Duplicate matches may share a representative location.
Review whether this belongs to intended app functionality or a bundled library. A static match does not establish runtime impact.
Preview evidence and Pro toolsSearch recorded evidence and save private review notes with Pro. $99/month plus applicable tax.
lowFirebase Storage bucket reference2 occurrences
Interpretation & review guidance
A Firebase Cloud Storage bucket reference (the default <project>.appspot.com). Storing user files here is normal — it's only an exposure if the Storage security rules allow public read/list, which live verification tests.
- Evidence
- 2 recorded occurrences in the analyzed APK. These are distinct stored findings, not a count of every source match.
- Verification
- Static detection; current reachability is not established.
Evidence preview
- Evidence type
- Static string match
- Representative location
lib/arm64-v8a/libchrome.so- Recorded match
Pattern recorded; identifying value redacted.- Detector rule
firebase_storage_bucket- Recorded file locations
lib/arm64-v8a/libchrome.so
2 recorded findings have inspectable metadata. Duplicate matches may share a representative location.
Review whether this belongs to intended app functionality or a bundled library. A static match does not establish runtime impact.
Preview evidence and Pro toolsSearch recorded evidence and save private review notes with Pro. $99/month plus applicable tax.
lowGoogle API key (client-shipped; restriction unverified)1 occurrence
Interpretation & review guidance
Android apps are designed to ship Google API keys in the client; Google restricts them by app signing certificate + enabled API. This is only a problem if the key is left unrestricted — presence alone is expected, not an exposure.
- Evidence
- 1 recorded occurrence in the analyzed APK. These are distinct stored findings, not a count of every source match.
- Verification
- Static detection; current reachability is not established.
Evidence preview
- Evidence type
- Static string match
- Representative location
lib/arm64-v8a/libchrome.so- Recorded match
AIza•••••••• (21–40 chars, redacted)- Detector rule
google_api_key- Recorded file locations
lib/arm64-v8a/libchrome.so
1 recorded findings have inspectable metadata. Duplicate matches may share a representative location.
Review whether this belongs to intended app functionality or a bundled library. A static match does not establish runtime impact.
Preview evidence and Pro toolsSearch recorded evidence and save private review notes with Pro. $99/month plus applicable tax.
No categories match these filters. Clear the search or choose all severities.
Privacy signals
Capabilities and bundled software do not prove that data was collected or transmitted.
Precise location Approx. location Camera Microphone List installed apps
Requested permission inventory (50)
Data collection & flow (privacy signal, not part of the grade)
- Personal-data permissions/identifiers appear on-device, but no third-party analytics/advertising SDKs were detected that would receive them.
This maps what the app can access (permissions it requests, identifier APIs its code references) to the third parties bundled in it. It reflects capability and SDK presence — not proof that a specific value was transmitted.
Data Safety comparison not recorded.
No SDKs detected by this scan.
Build & components
Scanned build 1.98.52. Store metadata may describe a newer release.
306270d4f94726831c5acb2e9e26ca5d1a2812411a5b5e1657701fdd6964e070Signing certificate (who signed this build — factual, not part of the grade)
9c:2d:b7:05:13:51:5f:db:fb:bc:58:5b:3e:df:3d:71:23:d4:dc:67:c9:4f:fd:30:63:61:c1:d7:9b:bf:18:acThe certificate fingerprint identifies the parsed signing certificate. Knowing this public fingerprint does not establish ownership or validate the APK signature.
Component inventory
No bundled components detected by this scan.
Export SBOMAbout this app · store information
About this app
Brave browser Beta (early-release preview version for testing & stability)
Screenshots
Scan history
Each row is an observed scan. Gaps between scans do not establish how long a finding existed.
| Scanned (UTC) | Build | Score | Grade |
|---|---|---|---|
| 2026-10-09 03:09 UTC | 1.98.52 | 97 | A |
| 2026-10-02 02:28 UTC | 1.98.47 | 97 | A |
| 2026-09-25 02:27 UTC | 1.97.47 | 97 | A |
Export & share
Exports describe the recorded assessment. Signed evidence proves origin and integrity, not completeness or safety.
Coverage & gap matrix · Verify signed evidence
Embed the latest grade
Embed this grade
The badge reads the latest recorded grade each time it is loaded, and links back to the full report so a reader can see the build it covers and what the scan could not see.
Grades can move when a new version is scanned or when a detector is corrected. If you would rather publish a grade that cannot change under you, link a signed Proof Capsule instead.
API users can request authenticated, scan-specific exports at /v1/scans/8a73893c-d0de-4a26-8235-3852da8e0977/findings.sarif (also coverage.json and proof.json).
Request a correction or removal · How to interpret a scan · Browse apps