Skip to content

Conversation

@christian-kreuzberger-dtx
Copy link
Collaborator

@christian-kreuzberger-dtx christian-kreuzberger-dtx commented Oct 16, 2025

Adds OSV dependency vulnerability scanning via GitHub Actions.

This workflow:

  • Runs on push & PR to main, plus a weekly scheduled scan (Mondays 03:00 UTC)
  • Uses the official OSV Scanner Action to detect known vulnerabilities: https://google.github.io/osv-scanner/github-action/
  • Converts results to SARIF and uploads them to GitHub Code Scanning (visible under Security → Code scanning alerts)
  • Complements existing Snyk scanning for broader coverage (different advisory sources)

References:

image

Copy link
Collaborator

@MrManny MrManny left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

250728_161417_581_3046_64.mp4

@github-advanced-security
Copy link

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.

@christian-kreuzberger-dtx
Copy link
Collaborator Author

I think we should configure the Workflow to not fail the build. It reports two findings, and we can't fix any of them right now...

@christian-kreuzberger-dtx christian-kreuzberger-dtx merged commit 40bf6a2 into main Oct 21, 2025
7 checks passed
@christian-kreuzberger-dtx christian-kreuzberger-dtx deleted the patch/add-osv-scanner branch October 21, 2025 06:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants