-
Notifications
You must be signed in to change notification settings - Fork 5k
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 reporting numerous security vulnerabilities in the current build #2744
Comments
I've created a branch called "audit" on my own fork in order to test the changes. Looks like it builds clean without errors, but tests are failing. However it looks like tests are failing on a clean pull of 1.0 for the same reasons. I'll open a separate issue for that. |
These issues are mostly because of |
Updated dependencies by
Manually updated dependencies: Nine "security vulnerabilities" are left because |
FYI, the latest version from the 1.x branch is reporting 1401 vulnerabilities (1378 low, 10 moderate, 13 high). |
Fwiw the only public facing vuln is for Web3 itself and relates to wallet storage. Everything else is in the development dependency tree. Root dependencies with sub-dependencies (like handlebars etc) flagged by High
Moderate
These are mostly tools used in CI. We are updating Lerna today. |
I was working on a clean fork of the master branch and on a lark I decided to run npm audit.
I'm always hesitant to trust automated tools, but I think it would be advisable for someone to take a look at what it's finding and determine what's what.
update
I opened and deleted some comments a little while ago believing I might be on an ancient branch. I double checked that I am on the 1.0 branch now and getting about the same results.
The text was updated successfully, but these errors were encountered: