Compare environments like evidence.
Go beyond spreadsheets by comparing software fingerprints, versions, hashes, signers, paths, package evidence, and scan provenance over time.
VersionGopher is moving toward a software evidence layer that compares environments like evidence, not inventory rows. The roadmap extends forensic ML, collection, protection, graph context, and integrations across enterprise, embedded, offline, mission, industrial, and autonomous systems.
Go beyond spreadsheets by comparing software fingerprints, versions, hashes, signers, paths, package evidence, and scan provenance over time.
Future releases will use analyst labels, accepted findings, dismissed noise, and organization-specific baselines to tune discovery and prediction without hiding the underlying evidence.
Org-scoped access, audit trails, envelope encryption, retention controls, and export policy make evidence usable in real organizations.
VersionGopher is expanding labeled CVE corpora, distro package truth, vendor advisories, and field regressions so matcher changes can be measured for false-positive reduction and true-positive retention.
Analysts need context: why a match exists, what else shares the hash, which scans changed, and which decisions have already been made.
Firmware captures, fielded devices, lab systems, embedded Linux, storage estates, UAVs, vehicles, and mission platforms should not be invisible.
SIEM, EDR, case management, legal, diligence, repository, and reporting workflows need software evidence with scope and rationale intact.
The roadmap keeps VersionGopher focused: collect software evidence, explain it, protect it, compare it, and hand it off. It should make SIEM, EDR, case management, legal, diligence, and repository workflows smarter without pretending to replace them.
Expose versions, hashes, signatures, packages, archives, and binary evidence.
Keep evidence scoped, auditable, encrypted where needed, and exportable with custody intact.
Connect evidence to CVEs, drift, analyst notes, mission context, and business decisions.
A firmware image, inherited environment, embedded platform, storage estate, or mission review is exactly the kind of target this roadmap is built around.