Future / Roadmap — not built yet
What PatchVex could become
if teams ask for it.
PatchVex today is two real, independent products: the free Web Scanner and the open-source VulnPilot CLI. Neither has accounts, cross-repo visibility, or organization-wide policy today. This page describes a possible future layer that would connect them for teams — described here honestly as a concept, not a shipped product, because we'd rather build this only once real usage justifies it.
The concept
A seven-stage model, not a seven-stage product.
This is how we think about a finding's lifecycle when designing future capabilities — it is not a live system, and the diagram below shows no real numbers because none exist yet.
Findings ingested from every connected scanner.
Deduplicated and mapped to a common schema across sources.
Ranked by composite risk after policy evaluation.
Exceptions granted with documented justification and expiry.
Assigned to engineering, tracked against a deadline.
Closed and re-scanned for confirmation.
Evidence exported for the reporting period.
Architecture concept
How this could work, if built.
Capabilities
What's real today vs. roadmap.
Every row below is labeled with its actual status. GA means it ships today in the Web Scanner or VulnPilot; Roadmap means it does not exist yet and is not scheduled — it's listed only to show the direction we're considering.
| Capability | Discover | Normalize | Prioritize | Decide | Remediate | Audit | Status |
|---|---|---|---|---|---|---|---|
| Web Scanner | GA | ||||||
| VulnPilot (CLI) | GA | ||||||
| Cross-repo Policy Engine | Roadmap | ||||||
| Cross-repo Exception Management | Roadmap | ||||||
| Cross-repo SLA Manager | Roadmap | ||||||
| Organization Evidence Vault | Roadmap | ||||||
| AI Assistant | Roadmap |