Skip to content
This repository has been archived by the owner on Sep 14, 2022. It is now read-only.

Swagger-tools are showing some security vulnerabilities when checked by twistlock or npm audit. #568

Open
GauravAccion opened this issue Jul 10, 2018 · 0 comments

Comments

@GauravAccion
Copy link

I am a firm believer of making APIs and microservices by using the Swagger framework. But when my project's audit happened, it did show some critical issues with swagger-tools.
The issues were related to using string npm module etc.
Can it be fixed so that the industry standard Swagger can be used more confidently? :)
Steps to reproduce -

  • create any API scaffolding by using swagger.
  • run npm audit command.
  • it will show the issues.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant