We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug Cloned react-slingshot and ran npm i with Node 12 and NPM 6. It reported a critical security vulnerability.
react-slingshot
npm i
To Reproduce Steps to reproduce the behavior:
Expected behavior Should not be any security vulnerabilities
Screenshots
/c/projects/react-slingshot (issue-625-period-404-fix)$ npm audit === npm audit security report === # Run npm update eslint-utils --depth 2 to resolve 1 vulnerability Critical Arbitrary Code Execution Package eslint-utils Dependency of eslint [dev] Path eslint > eslint-utils More info https://npmjs.com/advisories/1118 found 1 critical severity vulnerability in 1771232 scanned packages run `npm audit fix` to fix 1 of them.
Desktop (please complete the following information):
Additional context master head is at 207d66ed689642a50d9891cea86d63d8429f79ad Last commit in git log shows Aug 1.
207d66ed689642a50d9891cea86d63d8429f79ad
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Describe the bug
Cloned
react-slingshot
and rannpm i
with Node 12 and NPM 6. It reported a critical security vulnerability.To Reproduce
Steps to reproduce the behavior:
Expected behavior
Should not be any security vulnerabilities
Screenshots
Desktop (please complete the following information):
Additional context
master head is at
207d66ed689642a50d9891cea86d63d8429f79ad
Last commit in git log shows Aug 1.
The text was updated successfully, but these errors were encountered: