You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jul 29, 2024. It is now read-only.
I know this vulnerability is only applicable when request is used in a web app, but any users that are automating vulnerability checking (with Node Security Project or snyk etc.) will have failed builds with [email protected].
Maybe you should add some vulnerability checking in your build pipeline? This is the second time in a week I've raised an issue on this project about vulnerable dependencies.
The text was updated successfully, but these errors were encountered:
If this issue is causing a problem for your testing, feel free to reopen this bug with an example of the test with logs to show how this is causing a security problem for you. This is already a planned pull request and does not seem to be an issue for the next release of protractor.
In this case this isn't a security problem, rather an automation problem. But good news it looks like it'll naturally go away in the near future. Cheers!
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Protractor depends on [email protected] which has a vulnerability:
https://snyk.io/vuln/npm:request:20160119
I know this vulnerability is only applicable when request is used in a web app, but any users that are automating vulnerability checking (with Node Security Project or snyk etc.) will have failed builds with [email protected].
Maybe you should add some vulnerability checking in your build pipeline? This is the second time in a week I've raised an issue on this project about vulnerable dependencies.
The text was updated successfully, but these errors were encountered: