-
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
Known vulberabilites #126
Comments
What are you referring to? |
https://github.com/nodesecurity/nsp Additional some of Your dependencies also includes reported vulnerabilities. |
Hello I have the same issue, I'm using Swagger https://www.npmjs.com/package/swagger which in turn uses swagger-connect version 0.1.0. As I understand it swagger-connect is just a wrapper for this project swagger-node-runner. When I use nsp: https://www.npmjs.com/package/nsp . it gives me the following vulnerabilities: Any ideas how I can remove these vulnerabilities ? Thanks ! |
Yes. I suggest you upgrade. swagger-connect 0.1.0 is ancient, the current version is 0.7.0. The readme of this repo has information as to upgrading to a more modern version. |
Thank you for your response, if this version is so old, any ideas why it is being used as the default version when I run |
That's a good question, but one I can't properly answer. Here is the repo for that project: https://github.com/swagger-api/swagger-node. Perhaps they'd like help updating their templates to a recent version. |
Swagger node runner contains 2 know vulnerabilities in different dependence package, is any plan to use
newer version of that packages?
The text was updated successfully, but these errors were encountered: