Skip to content

ci(security): add warn-only Trivy dependency CVE scan (orb 1.6.0) - #766

Open
MarkusReadius wants to merge 9 commits into
masterfrom
ci/trivy-cve-scanning
Open

ci(security): add warn-only Trivy dependency CVE scan (orb 1.6.0)#766
MarkusReadius wants to merge 9 commits into
masterfrom
ci/trivy-cve-scanning

Conversation

@MarkusReadius

@MarkusReadius MarkusReadius commented Jul 3, 2026

Copy link
Copy Markdown
Member

What

  • Adds one CircleCI job, dependency-cve-scan, wired into run_tests (every PR and every non-publish push to master) and weekly_vulncheck (Monday 06:00 cron on master, alongside make vulncheck). Trivy filesystem scan over the checkout, reporting fixable CRITICAL/HIGH. The scan path is the repo root, so the root, v2 and v3 modules are all covered.
  • Warn-only: fail-on-findings: false. Results land in the job log, the artifacts and the CircleCI Tests tab.
  • Orbs become exact pins. arangodb/trivy-scan@1.1.2 is new; the pre-existing circleci/slack@4.1 float becomes 4.15.0, which is a minor bump as well as a pin since @4.1 resolves to 4.1.4 today. Both slack/notify call sites pass only channel, event and template, all still supported in 4.15.0.

Only .circleci/config.yml changes. No application code and no dependency versions are touched.

Why

A float resolves at config-compile time, so an orb publish changes what runs with no repo diff and no review.

The scan is warn-only because this is a client library: a fixable CVE in a transitive dependency should not block driver PRs, and consumers pin their own module versions. This buys visibility first. Making it an enforcing gate is a separate call for the team.

Notes

  • scanners is left at the orb default, so the job runs Trivy's default fs scanners, dependency CVEs plus secret detection. Both are warn-only here. Set scanners: vuln if this should be dependency-only.
  • Orb source is circleci_orbs/trivy-scan in arangoml/ai-infrastructure#69, still open.
  • Green on the head commit, dependency-cve-scan included.
  • Orb pin moved to 1.6.0 in this branch (engine trivy v0.73.0, checksum-paired).

… install fallback; nightly EOL+comprehensive where applicable)
Comment thread .circleci/config.yml
@MarkusReadius MarkusReadius changed the title ci(security): add warn-only Trivy dependency CVE scan ci(security): add warn-only Trivy dependency CVE scan (orb 1.0) Jul 28, 2026
Requested in review: the weekly master cron previously ran only the
govulncheck job, so dependency CVE drift was invisible between PRs.
Both were patch floats, which CircleCI resolves at config-compile time, so a
new orb publish changes what runs with no repo diff. 4.15.0 is the newest 4.x,
which is what the float resolves to today.
@MarkusReadius MarkusReadius changed the title ci(security): add warn-only Trivy dependency CVE scan (orb 1.0) ci(security): add warn-only Trivy dependency CVE scan (orb 1.1.2) Jul 30, 2026
@MarkusReadius MarkusReadius changed the title ci(security): add warn-only Trivy dependency CVE scan (orb 1.1.2) ci(security): add warn-only Trivy dependency CVE scan (orb 1.6.0) Aug 6, 2026
@MarkusReadius
MarkusReadius requested a review from jwierzbo August 7, 2026 01:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants