Skip to content

ci: add Trivy vulnerability scanning#372

Draft
skyrpex wants to merge 4 commits into
mainfrom
claude/trivy-workflow-setup-457554
Draft

ci: add Trivy vulnerability scanning#372
skyrpex wants to merge 4 commits into
mainfrom
claude/trivy-workflow-setup-457554

Conversation

@skyrpex

@skyrpex skyrpex commented Jul 8, 2026

Copy link
Copy Markdown
Contributor

Adds a GitHub Actions workflow that runs Trivy against the Go dependencies.

  • On PRs and pushes to main: fails the check on fixable CRITICAL/HIGH vulnerabilities.
  • Weekly: full scan across all severities.

Both upload results to the Security tab (code scanning), which annotates PRs inline and notifies watchers subscribed to security alerts.

Closes DEVX-837.

🤖 Generated with Claude Code

Blocking PR/main gate on fixable CRITICAL/HIGH Go dependency vulns, plus a
weekly full scan that reports to Slack on findings. Both upload SARIF to code
scanning (skipped on fork PRs).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@skyrpex skyrpex requested a review from a team as a code owner July 8, 2026 14:34
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@github-advanced-security

Copy link
Copy Markdown

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

  • The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
  • Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
  • You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

@skyrpex skyrpex added semver: patch docs: skip Pull request does not require documentation changes labels Jul 8, 2026
trivy-action ignores severity/ignore-unfixed when format is sarif and reports
all severities, so a single sarif step failed the gate on a low-severity
test-only CVE. Use a dedicated table-format gate step for CRITICAL/HIGH.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@skyrpex skyrpex marked this pull request as draft July 8, 2026 14:51
Upload SARIF to the Security tab so alerts flow through GitHub-native
notifications (watchers subscribed to security alerts), dropping the Slack
webhook, jq summary, and SLACK_WEBHOOK_URL secret.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

docs: skip Pull request does not require documentation changes semver: patch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants