VEX Integration with Vulnerability Explorer

Audience: engineers wiring VEX evidence into the Vulnerability Explorer and triage surfaces.

In Stella Ops, the Vulnerability Explorer and its triage surfaces treat VEX as first-class evidence: operator decisions should be explainable, replayable, and linked to provenance.

Triage View Expectations

• Show effective VEX status alongside policy outcome and reachability/impact signals.
• Make conflicts visible and navigable (issuer list, trust tiers, verification state).
• Provide deep links from the triage view into VEX evidence (raw observations/linksets) and to policy explain traces.

Filtering and Lanes

VEX evidence commonly affects:

• Default lane placement (e.g., MUTED_VEX vs ACTIVE)
• Whether a finding is actionable, needs exception, or can be shipped
• Staleness warnings for offline snapshots

The Explorer must remain “quiet by default, never silent”: VEX-based suppression should be reversible and auditable, not a destructive delete.

References

• docs/VULNERABILITY_EXPLORER_GUIDE.md — conceptual triage model and determinism requirements
• VEX consensus guide
• Vulnerability Explorer CLI guide
• VEX consensus in the Console