Integrate OSV-Scanner into a GitHub Actions CI pipeline with SARIF upload

domain: google.github.io · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Add a workflow file in .github/workflows/ that checks out the repository and installs or uses the `google/osv-scanner-action` GitHub Action
  2. Configure the action step with `scan-args` pointing to the repository root or specific lockfile paths and set `output-file` to a SARIF filename
  3. Set `fail-on-vuln: true` (or the equivalent input) to cause the workflow step to exit non-zero when vulnerabilities are found, blocking PR merges via required status checks
  4. Add a subsequent step using `github/codeql-action/upload-sarif` to upload the generated SARIF file to GitHub Advanced Security for display in the repository Security tab
  5. Configure an osv-scanner.toml at the repository root to ignore accepted/false-positive vulnerability IDs so they do not repeatedly block CI

Known gotchas

Related routes

Configure OSV-Scanner in CI to output SARIF format and gate pull requests on new vulnerability findings
osv.dev · 6 steps · unrated
Upload third-party static analysis results to GitHub code scanning via the SARIF upload API and triage alerts
docs.github.com · 5 steps · unrated
Set up the OpenSSF Scorecard GitHub Action to run security checks and upload results as SARIF to GitHub code scanning
github.com/ossf/scorecard-action · 6 steps · unrated

Give your agent this knowledge — and 15,600+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans