-
Notifications
You must be signed in to change notification settings - Fork 478
Critical Vulnerability in @expo/webpack-config #4396
Comments
There are more vulnerabilities today, see below node-forge
browserslist
ansi-html
I think there are other outdated dependencies, this list is not exhaustive. You should consider upgrading This issue prevents us from using this package, and it is necessary for us to build in web mode. : / |
Hadn't seen this issue when posted #4570 (comment) |
https://overreacted.io/npm-audit-broken-by-design/ Please explain to me how a tool you are running locally compromises the security of your app/web project. |
@kbrandwijk , Yeah... "safe" also meaning a safe place to be investing time...which admittedly wasn't obvious. I can't know what exactly webpack is doing with my files - what, if anything it is adding to the possibly tens of thousands of project files I'll end up with to generate the final build so I don't know without a whole lot of effort (that kind of negates the whole point of using the tools) IF what the tools are telling me are critical security issues are in fact going to be security issues. Sure, while I'm working on my machine locally etc. I can carry on .. and get to the next set of issues, but come the time for a release build if npm audit says I have security issues and I can't explain every one of them away then I have a problem. Bottom line: I should not be seeing this output. |
react-dev-utils is no longer used as of #3763 |
Summary
yarn audit
shows https://www.npmjs.com/advisories/1005029 as a critical vulnerability, due to an old version ofreact-dev-utils
.Environment
Please specify your device/emulator/simulator platform, model and version
N/A
Error output
as well as
Reproducible demo or steps to reproduce from a blank project
The text was updated successfully, but these errors were encountered: