Add npm audit and list output to OSV PR comments. #14
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
This is headed toward being a shared GitHub Action, so it can be run on both the old code and the new/latest code (without copying and pasting...).
BigBlueHat
force-pushed
the
add-npm-audit-list
branch
from
e778562 to
8d54bd8
Compare
This also now generates reports for the old and new code separately.
This action is new to the repo and it will fail on the old branch, so we are continuing on error in that case.
Otherwise we have to download the entire node_modules/ just to check the same data.
Local tests did not need this...but apparently the runner in the cloud does.
BigBlueHat
requested review from
davidlehn,
dlongley,
mandyvenables and
tminard
dlongley
approved these changes
Oct 11, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR is to address @davidlehn's concerns around developers not knowing how to find the correct replacements for a vulnerable dependency. In addition to the CVE links provided by OSV (which have been there from the beginning), the scanner now also provides an
npm auditreport showing available replacement versions as well as annpm listresult filtered on the vulnerable dependencies for the frequent case when the vulnerability is in a secondary (or "lower") dependency.Hopefully this helps ease developer research time and speeds resolution of vulnerability issues.