update high vulnerability node modules #2303
Merged
Conversation
This file contains 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
BenSurgisonGDS
force-pushed
the
fix-high-vulnerability-node-modules
branch
from
d2709ad
to
9b76c10
Compare
BenSurgisonGDS
added
🕔 Hours
BenSurgisonGDS
force-pushed
the
fix-high-vulnerability-node-modules
branch
from
9b76c10
to
772d0ad
Compare
BenSurgisonGDS
force-pushed
the
fix-high-vulnerability-node-modules
branch
from
59f0534
to
8f374f7
Compare
nataliecarey
approved these changes
Aug 24, 2023
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.
Upated nodemon due to high vulnerability detection from user
What
User reported the kit contained high vulnerability node modules and asked for them to be updated.
Why
The prototype kit should not be the reason the users prototypes fail a high vulnerability check.
Who needs to work on this
Who needs to review this
Done when