feat: add VEX automation for closed issues #225
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
RafaelGSS
reviewed
Jan 30, 2026
| Automated checks are currently run through a GitHub action using | ||
| [dep_checker](https://github.com/nodejs/nodejs-dependency-vuln-assessments/tree/main/dep_checker). | ||
|
|
||
| When issues are closed with specific labels (e.g., `vulnerable_code_not_in_execute_path`), |
Member
There was a problem hiding this comment.
Can you include the docs for all the other labels?
Author
There was a problem hiding this comment.
sure it will not be a problem just a little context how deep i have to go
Member
There was a problem hiding this comment.
we need to include a list of labels we need to create, they need to match the vex spec
Member
|
Overall looks good to me, it lacks some documentation and checking if vuln already exists in the database |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
feat: add VEX automation for closed issues
When an issue is closed with labels like vulnerable_code_not_in_execute_path, this automation creates a PR in nodejs/security-wg with the VEX entry.
Setup required by maintainers:
Add SECURITY_WG_TOKEN secret with write access to nodejs/security-wg
Closes #224