feat: automate VEX entry creation in nodejs/security-wg on issue close - #436
Open
marco-ippolito wants to merge 1 commit into
Open
marco-ippolito wants to merge 1 commit into
marco-ippolito wants to merge 1 commit into
Conversation
RafaelGSS
approved these changes
Sep 23, 2026
Member
|
@marco-ippolito you might need to change the Co-Authored-By to Assisted-By. |
…stification label Closing an issue with one of the five OpenVEX `not_affected` justification labels now runs the `vex-entry` workflow, which generates a `vuln/deps/<N>.json` entry and opens a pull request against nodejs/security-wg. CVEs already recorded in `vuln/deps` are skipped, so the per-release-line duplicates of the same CVE do not produce duplicate entries. The README documents the labels, the affected path (`confirmed`), the legacy labels, and the `SECURITY_WG_TOKEN` secret the workflow needs. Supersedes #225. Closes #224 Co-Authored-By: sddhantjaiii <122254271+sddhantjaiii@users.noreply.github.com> Assisted-By: Claude Fable 5.1 <noreply@anthropic.com>
marco-ippolito
force-pushed
the
feat/vex-entry-automation
branch
from
September 25, 2026 12:42
09860a9 to
e172804
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Supersedes #225 (thanks @sddhantjaiii, credited as co-author).
Closes #224
What
Closing an issue with exactly one of these labels opens a PR in nodejs/security-wg adding a
vuln/deps/<N>.jsonentry withstatus: not_affectedand the label asreason:component_not_presentvulnerable_code_not_presentvulnerable_code_not_in_execute_pathvulnerable_code_cannot_be_controlled_by_adversaryinline_mitigations_already_existThe five labels have been created on this repo.
confirmedremains the "affected" signal and is documented as handled by the security release process viavuln/core.dont-believe-affects-nodejsanddont-fall-in-threat-modelare documented as legacy and do not trigger anything.How the entry is built
cve: every CVE id in the issue title. CVEs already invuln/depsare skipped, so closing the v22/v24/v26/main duplicates of one CVE does not create duplicate entries. The security-wg branch is named after the first new CVE, so a second closure updates the existing PR instead of opening another.description: CVE record title from the cve.org API (no key needed).overview: latest comment by the person who closed the issue, falling back to a generic sentence per label.ref: the issue URL.The workflow comments on the closed issue with the security-wg PR link, or with the reason it did nothing.
Verification
dep_checker/test_vex_entry.py, run by the newtest.ymlworkflow on Python 3.9.7.jsonpassednpm run create-deps-indexand the Go VEX generator's validators, producing anot_affectedstatement withjustificationandimpact_statement.Setup needed before merge
Add a
SECURITY_WG_TOKENrepository secret withcontents: writeandpull-requests: writeon nodejs/security-wg.🤖 Generated with Claude Code