[Snyk] Fix for 24 vulnerabilities

[snyk-io]

Snyk has created this PR to fix 24 vulnerabilities in the npm dependencies of this project.

Snyk changed the following file(s):

• workspaces/arborist/test/fixtures/tap-with-yarn-lock/node_modules/log-driver/package.json
• workspaces/arborist/test/fixtures/tap-with-yarn-lock/node_modules/log-driver/.snyk

Vulnerabilities that will be fixed with an upgrade:

	Issue
	Regular Expression Denial of Service (ReDoS) SNYK-JS-HAWK-2808852
	Authentication Bypass SNYK-JS-HAWK-6969142
	Denial of Service (DoS) SNYK-JS-JSYAML-173999
	Arbitrary Code Execution SNYK-JS-JSYAML-174129
	Regular Expression Denial of Service (ReDoS) SNYK-JS-MINIMATCH-1019388
	Regular Expression Denial of Service (ReDoS) SNYK-JS-MINIMATCH-3050818
	Regular Expression Denial of Service (ReDoS) SNYK-JS-MOCHA-2863123
	Regular Expression Denial of Service (ReDoS) SNYK-JS-MOCHA-561476
	Improper Privilege Management SNYK-JS-SHELLJS-2332187
	Arbitrary Code Injection SNYK-JS-UNDERSCORE-1080984
	Insecure use of /tmp folder npm:cli:20160615
	Arbitrary Code Injection npm:growl:20160721
	Cross-site Scripting (XSS) npm:handlebars:20151207
	Regular Expression Denial of Service (ReDoS) npm:hawk:20160119
	Prototype Pollution npm:hoek:20180212
	Regular Expression Denial of Service (ReDoS) npm:mime:20170907
	Regular Expression Denial of Service (ReDoS) npm:minimatch:20160620
	Denial of Service (DoS) npm:qs:20140806
	Denial of Service (DoS) npm:qs:20140806-1
	Prototype Override Protection Bypass npm:qs:20170213
	Remote Memory Exposure npm:request:20160119
	Uninitialized Memory Exposure npm:tunnel-agent:20170305

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.
• Some vulnerabilities couldn't be fully fixed and so Snyk will still find them when the project is tested again. This may be because the vulnerability existed within more than one direct dependency, but not all of the affected dependencies could be upgraded.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Cross-site Scripting (XSS)
🦉 Regular Expression Denial of Service (ReDoS)
🦉 Authentication Bypass
🦉 More lessons are available in Snyk Learn

[sourcery-ai]

🧙 Sourcery is reviewing your pull request!

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time. You can also use
  this command to specify where the summary should be inserted.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.