Executable evidence got richer.
PE, Mach-O, ELF, archives, signatures, hashes, hardening clues, and suspicious-file indicators are easier to review from the file outward.
This release moves VersionGopher beyond inventory. A scan can now carry stronger binary evidence, safer CVE rationale, hash correlation, package advisory context, and buyer-ready reporting from normal enterprise systems and the embedded or offline assets that most tools cannot see.
PE, Mach-O, ELF, archives, signatures, hashes, hardening clues, and suspicious-file indicators are easier to review from the file outward.
Component scope, vendor/platform context, weak-version handling, and visible rationale reduce noisy matches without hiding real exposure.
Signed and synchronized collector releases support enterprise systems plus ARM, OpenWrt/Entware ARMv7, MIPS, and PowerPC targets where available.
Teams can correlate SHA-256 evidence, trusted malware-hash hits, package-risk advisories, and Miasma-response scans without live reputation lookups per file.
CVE exposure, package risk, private-key and wallet exposure metadata, archive evidence, drift, and scan provenance can be packaged for review.
VersionGopher 0.7.5 helps responders, security leaders, diligence teams, and mission owners move from raw file lists to evidence-backed action: what is present, what is risky, what changed, what deserves follow-up, and what can be shown to stakeholders without pretending the environment was cleaner than it really was.
The release keeps the collector lightweight and moves analysis into the hosted workflow: file cards, CVE panels, package-risk views, binary forensic signals, search, drift, and assessment reports.
Open technical help and setup notes
Start with one endpoint group, firmware image, storage estate, inherited environment, or embedded platform.