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 has been archived by the owner on Sep 14, 2022. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 -
The text was updated successfully, but these errors were encountered: