Skip to content

Add vulncheck to dev-v2#1713

Open
karensantana wants to merge 3 commits into
dev-v2from
add-vulncheck-dev-v2
Open

Add vulncheck to dev-v2#1713
karensantana wants to merge 3 commits into
dev-v2from
add-vulncheck-dev-v2

Conversation

@karensantana

Copy link
Copy Markdown
Contributor

Proposed changes

This PR adds automated vulnerability scanning to the dev-v2 branch.
Currently, the dev-v2 workflow does not perform vulnerability checks, which means newly introduced dependencies or changes are not automatically evaluated for known security issues. To improve security visibility and catch vulnerabilities earlier in the development cycle, this PR introduces two new scanning triggers:

Push-based scanning: Run a vulnerability scan whenever code is pushed to the dev-v2 branch.
Scheduled scanning: Run a nightly vulnerability scan to identify newly disclosed vulnerabilities in existing dependencies, even when no code changes have been made.

Checklist

Before creating a PR, run through this checklist and mark each as complete.

  • I have read the CONTRIBUTING document
  • I have run make install-tools and have attached any dependency changes to this pull request
  • If applicable, I have added tests that prove my fix is effective or that my feature works
  • If applicable, I have checked that any relevant tests pass after adding my changes
  • If applicable, I have updated any relevant documentation (README.md)
  • If applicable, I have tested my cross-platform changes on Ubuntu 22, Redhat 8, SUSE 15 and FreeBSD 13

@karensantana karensantana requested a review from a team as a code owner June 3, 2026 10:33
@github-actions github-actions Bot added the documentation Improvements or additions to documentation label Jun 3, 2026
@karensantana karensantana mentioned this pull request Jun 3, 2026
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants