-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
6 high severity vulnerabilities - Inefficient Regular Expression Complexity in nth-check #7
Comments
Amy - I am going to assign this issue to you just to test the process of finding and fixing issues. Please comment (or re-assign to fix) |
Testing testing. |
Not sure how to "reassign to fix"...? |
Oh - I just meant change the "assignees" on the right. So if you think someone from the people you were working with last night in the Armadillo Room could benefit by taking on this "learning opportunity", change the assignee from you to someone else. (The fix is simple. After fixing I got a |
Re-opening. See comment in merge commit. #8 |
@koto253 this issue has been reopened. I shared a fix with you in Discord if you'd like to create a new PR to fix it. |
Tested on my app. "found 0 vulnerabilities" |
na I take that back. didn't stash my changes b4 pull (rookie mistake). Re-opening |
I implemented the suggested fixes. Currently showing 0 vulnerabilities. Moving to ready to be staged
|
The latest commit shows the following message with a
npm audit
Please resolve the vulnerabilitiesa suggested fix is here
The text was updated successfully, but these errors were encountered: