// REPORT
Reading a report
The report is built as evidence, not a counter: every finding carries its place in the binary and a slice of source context. A map of the sections follows.
SEVERITY
The scale
Five levels. Critical: an extractable secret with direct damage, or a remote command with real permissions. High: combinations exploitable without special conditions. Medium: needs preconditions (a debug signature, weak configuration). Low and info: hygiene.
EVIDENCE
File and line
Each finding quotes the file and line: classes.dex, res/values/strings.xml, assets/config.json or a native library. Secrets print masked (sk_live_••••0002): recognizable, not reusable.
MASVS
The mapping
The OWASP MASVS row shows which requirement a finding contradicts (STORAGE, CRYPTO, PLATFORM, RESILIENCE). An auditor reads that faster than a raw list.
CVSS
The score
A CVSS v3.1 score from the usual AV/AC/PR vector. The report sorts by it, not by category alphabet.
SBOM
Inventory
The SBOM button exports CycloneDX 1.5: every library with a version, native ones included. Useful for inventory and for comparing two builds.
DIFF
Comparing versions
When the same package was scanned before, the report shows Changes since: new secrets, permissions, SDKs and exported components as separate chips. An SDK update becomes visible before it ships to users.
A file for email
The PDF button packs the same into a file for email: header, severities, MASVS, findings, SBOM, native analysis. No signature needed; the tokenized web link is the source of truth.