Patch release: ingest robustness, recommended Trivy 0.73.0, and an agent-side Trivy DB metadata fix. No schema change, no migration — upgrade in place.
TICKET-023: Trivy DB metadata read after the scan, not before
Fixed
- The agent now reads
trivy version --format jsonafter therootfs
scan instead of before it, so the reported DB version/timestamps reflect
the DB the scan actually used. Previously a host whose DB refreshed
during the scan submitted fresh findings but reported the pre-scan DB
state, showing atrivy-db stalepill that was already wrong. Agent-side
only — server, schema and UI are unchanged.
Changed
AGENT_VERSION/CURRENT_AGENT_VERSIONbumped0.10.0→0.11.0so
the fix reaches hosts viaauto_update_self. Hosts pick it up on their
next run; no backfill of existingservers.trivy_db_*rows.
TICKET-022: bump recommended Trivy to 0.73.0
Changed
RECOMMENDED_TRIVY_VERSIONraised from0.71.0to0.73.0. Every host
with a fathometer-managed Trivy binary picks up the new version on its
next scheduled run via the existingauto_update_trivymechanism —
server-side only, no agent update needed.MIN_TRIVY_VERSIONstays
0.70.0; hosts on a system-package Trivy are unaffected.
TICKET-021 (ADR-0072): per-vulnerability ingest leniency
Fixed
- A single non-conforming vulnerability entry no longer discards the whole
scan (#22,
#23):
Vulnerabilitiesis validated per entry, so a bad entry drops itself while
the remaining findings ingest. Accepted identifiers now coverTEMP-*
(Debian Security Tracker),DSA,DLA,RUSTSEC,GOandPYSECnext to
CVE and GHSA; over-longTitle/Descriptionare trimmed instead of
rejected. Server-side only — no agent update needed, previously failed scans
are not backfilled. - Bulk-acknowledge by identifier accepts the same identifier set, so non-CVE
findings can be acknowledged in bulk.
Added
- Dropped entries are counted per scan and reported as
vulns_droppedin the
scan.ingestedaudit metadata, the scan-ingest job result and the log.
Full changelog: v0.28.0...v0.28.1