DevGuard Vulnerability Events API
DevGuard does not overwrite the state of a vulnerability when something changes. It appends an event — detected, accepted, marked false positive, mitigated, reopened — and the current state is what that sequence adds up to. This API reads that history.
You can pull the events for one finding when you need to explain how it reached its present state, or for an entire asset version when you need the audit trail across everything. Both dependency vulnerabilities and first-party vulnerabilities expose their own event streams.
Deleting an event is available but rarely the right move: it rewrites history that compliance evidence may depend on. Reach for a corrective event instead, and keep deletion for entries created in error.
Related Documentation
- Create Vulnerability Events — adding events
- Vulnerability Events Explained — the event model
- Vulnerability Lifecycle — the states events move through
- Audit Trails — why the history is append-only
- Vulnerabilities API — the findings these events belong to
- Track Fix Progress — using events to measure remediation
- Use the DevGuard API — authentication and conventions
- DevGuard API Reference