-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Vulnerability 1012 #2118
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
Comments
It is development server, so this security problem is not high priority here, also we don't use |
I did, i actually created a PR but i was curious if you guys were actively engaging is all |
Let's keep open for tracking |
For me it looks like I suddenly went from 0 vulnerabilities to uh... 765? I guess there is сombinatorial explosion involved. |
Problem was on npm side, now we doesn't have any vulnerability, thanks for issue |
Team,
https://www.npmjs.com/advisories/1012 was just raised today. It looks like it's based in
http-proxy-middleware
do you guys have an estimate on how long you think it'll take to get a release out that'll resolve this?it looks like
cache-base
may be the bottleneck hereThe text was updated successfully, but these errors were encountered: