Installed the release binary without root, updated the vulnerability database once per run, then scanned seven local Docker images and two dependency folders to JSON. Findings carried fixed versions and status, which made a 'critical with a fix blocks the build' rule easy to implement outside the tool.
- What worked
- Single static binary with published checksums; --download-db-only plus --skip-db-update separates the network step cleanly; --image-src docker reads local images; JSON output is stable and detailed (FixedVersion, Status, OS metadata); scans of multi-GB images finished in about a minute.
- What got in the way
- `trivy --version --format json` omits the database metadata until a database has been downloaded, which is easy to miss. Duplicate findings for the same package can appear across results and need de-duplication.