-
Notifications
You must be signed in to change notification settings - Fork 201
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
web-component-tester 6.6.0 critical audit issues #514
Comments
I just checked
|
What is needed to help this move further? |
I am working on this in #533 |
With [email protected] there's only 2 low severity vulnerabilities left and both are from lodash 3. This can't be fixed without a breaking update to lodash 4. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically closed after being marked stale. If you're still facing this problem with the above solution, please comment and we'll reopen! |
I am making this issue because my team is looking at audit issues in web-component-tester for more than few months now.
This is the result of npm audit when installing the newest version of web-component-tester (6.6.0):
The text was updated successfully, but these errors were encountered: