Fix: Upgrade yargs to ^16.0.0
See original GitHub issueHi,
There is a patch to a high severity vulnerability available for yargs
. Can you please update to version ^16.0.0
or so? It would resolve CVE-2020-7774.
https://snyk.io/test/npm/yargs/15.3.1
Thank you in advance!
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (3 by maintainers)
Top Results From Across the Web
Upgrade yargs to 16.0.0 to fix prototype pollution high ... - GitHub
Bug Report I am unable to use react-scripts@4.0.1 for work due to a high vulnerability security issue with jest@26.6.3 pulling in ...
Read more >yargs-parser vulnerabilities | Snyk
version published direct vulnerabilities
21.1.1 4 Aug, 2022 0. C. 0. H. 0. M. 0. L
21.1.0 3 Aug, 2022 0. C. 0. H. 0....
Read more >CHANGELOG.md | yargs@v16.1.0-deno
16.0.0 (2020-09-09). ⚠ BREAKING CHANGES. tweaks to ESM/Deno API surface: now exports yargs function by default; getProcessArgvWithoutBin becomes hideBin; ...
Read more >npm audit fix --force is not fixing any problems
Also no success. npm is at version 7.12.1 npm audit fix does not do a damn ... yargs-parser <=13.1.1 || 14.0.0 - 15.0.0...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Good callout Jamie.
On Mon, Nov 30, 2020 at 8:42 PM Jamie Peabody notifications@github.com wrote:
Note that this change should be a breaking change. Previously, copyfiles would work on node 8.x as it was using yargs 15.3.1, which was using engines >= 8. Now, copyfiles uses yargs 16.1.0, using engines >= 10.