v1.2.0
Current releaseBuild details: where a file was built, and what it gives away
A new Build tab reads where a PE or ELF file was built, what built it, which commit it came from and what it pulled in. It also checks the file for things you may not mean to ship, such as your account name in build paths, an internal host, or a complete token like a Stripe live key. Very large files opened from disk now show their version resource, PDB path and ELF sections.
See the Build tab →New
- Build tab for PE and ELF files. It shows the source commit (from version strings such as 7.0.0+d099f07…), PDB paths, the build root, the compiler and linker, the Go version and build settings from Go build info, the Rust version, and the Rust crates and Go modules the file was built with, with versions. Every row says how it is known (recorded by the file, or suggested by its strings) and links to the bytes in Hex or Strings.
- CI layouts are recognised from build paths: Azure Pipelines, GitHub Actions, GitLab Runner, Jenkins, TeamCity, CircleCI and Mozilla Taskcluster. They are shown as consistent with the path, not as proof, because CI folders can be configured.
- Leak check. The Build tab lists account names in build paths, internal hosts and network shares, and complete token shapes (Stripe live keys, GitHub, Slack and npm tokens, PEM private keys, and AWS key IDs, which are flagged more strongly when their secret key sits beside them). Values are masked on screen and in exports unless you choose Reveal, and nothing is checked online. Each finding comes with a fix that says what it covers and what it doesn't.
- A one-line Build summary on the Overview, with a link to the tab.
- Compare > Build shows what changed between two builds: toolchain and dependency versions, and leaks added or removed.
- Folder view: an Audit menu groups Verify Signatures, Audit Hardening and the new Build Info pass, which adds a Build column. Sorting it lists files with findings first, then the files that record the most about their build.
- Settings: list your own internal domains, and hosts and shares under them are listed in the Build tab. Build can also be chosen as the default tab.
- Tools > Export report includes a Build section in JSON and Markdown.
Improved
- Very large files (opened from disk rather than memory) now show their version resource, PDB path and ELF section headers, which used to come back empty. Anything that can't be read is named, never shown as missing.
- Compare now says why the Strings or Build tab is missing when one file was opened from disk.
- Stop in the folder view ends a pass at once, and closing a tab stops its background work.