-
Notifications
You must be signed in to change notification settings - Fork 9k
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
NPM audit advisory 1556 due to node-fetch dependency #6437
Comments
@restfulhead Yup, it's on our radar, and as you noted, we need to wait for a |
Hi Is there any update on this issue as we are not able to build the branch because of this issue because jenkins fails our build. |
There's a new release of |
@tim-lai Any updates? |
To those tracking this issue, here is some background: This is most likely a false positive via the React@15 library, specifically with SwaggerUI has a sub-dependencies that uses a version of I'm keeping this ticket open for now, hoping that we will eventually get a minor version update from either References: facebook/react#19840 FYI, this is the current result of
|
Hello @tim-lai, is there any plans on your part to update your dependencies for the remaining packages you mention as a result of the npm audit ? As this would mean bumping your react version by one major, I know it would be quite an endeavor but still asking. Thanks |
All these issues were addressed during v4 release effort. Using [email protected] and running following command: $ npm audit --verbose --production produces
We know we have some vulnerabilities in our development dependencies, but they pose no risk to the swagger-ui npm distribution. I'm closing this issue as IMHO the original subject has been addressed (reopen if I'm mistaken). |
Q&A
Expected behavior
npm audit
should not report any issues.Actual behaviour
Additional notes
Downstream issue: facebook/react#19840
Downstream root issue: matthew-andrews/isomorphic-fetch#189
Guess we'll have to wait until
isomorphic-fetch
releases a 2.x version.The text was updated successfully, but these errors were encountered: