-
-
Notifications
You must be signed in to change notification settings - Fork 49
1.4.0, npm audit issues #1107
Comments
#1105 |
Closing as duplicate to #1105 |
That's very nice it's a duplicate. But is there any actual intent to fix it? I mean it's a security issue, should be high on the team's list, should not it? NB: it's not a true duplicate as #1105 is about 1.3.0 and this one is about 1.4.0 |
@dmytro-gokun usually security issues are high priority, especially on the web. That said, app environments are very controlled and all the needed JS is packaged into the final bundle (no external JS can be injected). Most of the time, a XSS vulnerability will not affect a NS/RN app. The other vulnerability you posted (Out-of-bounds Read) is used by I'm obviously not saying they shouldn't be fixed, just giving a context as to why they might be considered low priority issues, which is why users are welcome to submit PRs to fix them (see #1105 (comment)), especially considering these might very easy fixes (update packages and run tests). |
When doing npm install, I get some audit warnings:
The text was updated successfully, but these errors were encountered: