-
Notifications
You must be signed in to change notification settings - Fork 124
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
Security: update package use of qs library #97
Comments
Created PR #98 |
Thanks! Can you please publish to NPM? |
Hello, is there any special reason this is still not being published to NPM after 9 days? I don't want to state the obvious from the referenced security links above, by Camsjams, but the qs vulnerability is a high severity one. Is this project not a really important one? Or is someone really sure that it cannot be exploited with swagger-node-runner? |
Sorry for the delay. It has been published as 0.7.3. |
Thanks! |
There is an advisory for the npm package qs that can be solved by upgrading to the latest version (currently at v6.4.0), or at the very least v6.1.2.
Some additional info from snyk and the qs github issue.
Should be a simple bump as there haven't been too many changes from 5 to 6 that would break.
The text was updated successfully, but these errors were encountered: