Use the public release fast
Choose installer or portable, launch the app, and know what the packaged build already includes.
documentation
Short docs for the questions people usually have first
The goal here is practical coverage: how to run the app, how to read the report, how URL and IP targets are handled, and what the current source-build path expects.
Read the output the right way
Understand what the verdict means, which sections deserve more weight, and where calibration matters.
Build from source when you care about internals
Qt, CMake, Visual Studio, MASM, and release-support notes are documented so the project stays inspectable.
Use the app
Getting started
Which package to download, what the public build already includes, and what BinaryLens is supposed to help you do on the first pass.
installer vs portable what the packaged build already includes what the first-pass workflow is meant to solve
Understand the report
Reading a BinaryLens report
How to interpret the report sections, what to trust more carefully, and why some signals are calibrated instead of pushed straight into over-escalation.
target type comes first stronger evidence should outrank isolated weak signals archives and compressed containers need calibration
Network targets
URL and IP analysis
How BinaryLens separates URLs, hostnames, and raw IPs, plus the kind of ownership and infrastructure context it can surface during the first pass.
raw IPv4, raw IPv6, hostnames, and URLs are handled differently provider and ASN context can make the first pass less generic ownership clues are evidence, not proof of intent
Optional enrichment
VirusTotal configuration
How the optional VirusTotal integration fits into the project, where the API key goes, and how to think about external reputation in the report.
VirusTotal is optional, not required for the app to run config.json is the normal project path for the API key external reputation should support the verdict, not replace it
Source build
Building from source
The current source-build expectations for BinaryLens, including Visual Studio, CMake, Qt, MASM, and the release-support files used for packaging.
Visual Studio + CMake project flow Qt 6.10.2 and MASM expectations portable and installer packaging files already exist in the repo