[Snyk] Fix for 15 vulnerabilities

[titanism]

Snyk has created this PR to fix 15 vulnerabilities in the yarn dependencies of this project.

Snyk changed the following file(s):

• package.json

Note for zero-installs users

If you are using the Yarn feature zero-installs that was introduced in Yarn V2, note that this PR does not update the .yarn/cache/ directory meaning this code cannot be pulled and immediately developed on as one would expect for a zero-install project - you will need to run yarn to update the contents of the ./yarn/cache directory.
If you are not using zero-install you can ignore this as your flow should likely be unchanged.

⚠️ Warning

Failed to update the yarn.lock, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Prototype Pollution SNYK-JS-PROTOBUFJS-5756498	751
	Prototype Poisoning SNYK-JS-QS-3153490	696
	Code Injection SNYK-JS-LODASH-1040724	681
	Code Injection SNYK-JS-LODASHES-2434284	681
	Regular Expression Denial of Service (ReDoS) SNYK-JS-BABELRUNTIME-10044504	666
	Regular Expression Denial of Service (ReDoS) SNYK-JS-PATHTOREGEXP-7925106	666
	Regular Expression Denial of Service (ReDoS) SNYK-JS-LODASH-1018905	586
	Regular Expression Denial of Service (ReDoS) SNYK-JS-LODASHES-2434289	586
	Information Exposure SNYK-JS-SANITIZEHTML-6256334	586
	Uncontrolled Resource Consumption SNYK-JS-GRPCGRPCJS-7242922	559
	Information Exposure SNYK-JS-NODEFETCH-2342118	539
	Prototype Pollution SNYK-JS-IOREDIS-1567196	531
	Regular Expression Denial of Service (ReDoS) SNYK-JS-BRACEEXPANSION-9789073	508
	Regular Expression Denial of Service (ReDoS) SNYK-JS-MINIMATCH-3050818	479
	Improper Input Validation SNYK-JS-POSTCSS-5926692	479

---

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.

---

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:

🦉 Regular Expression Denial of Service (ReDoS)
🦉 Prototype Pollution
🦉 Code Injection
🦉 More lessons are available in Snyk Learn

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	json-schema@​0.2.3
	number-is-nan@​1.0.1
	typedarray@​0.0.6
	pinkie-promise@​2.0.1
	get-caller-file@​1.0.3
	invert-kv@​1.0.0
	set-blocking@​2.0.0
	ansi-regex@​2.1.1
	forever-agent@​0.6.1
	aws-sign2@​0.7.0
	tunnel-agent@​0.6.0
	oauth-sign@​0.9.0
	is-utf8@​0.2.1
	is-typedarray@​1.0.0
	code-point-at@​1.1.0
	strip-bom@​2.0.0
	ecc-jsbn@​0.1.2
	require-main-filename@​1.0.1
	performance-now@​2.1.0
	load-json-file@​1.1.0
	string-width@​1.0.2
	getpass@​0.1.7
	which-module@​1.0.0
	is-fullwidth-code-point@​1.0.0
	throttleit@​1.0.0
	fast-json-stable-stringify@​2.1.0
	jsbn@​0.1.1
	isstream@​0.1.2
	buffer-from@​1.1.1
	pinkie@​2.0.4
See 44 more rows in the dashboard

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert (click for details)
Warn		[email protected] has a Critical CVE. CVE: GHSA-896r-f27r-55mw json-schema is vulnerable to Prototype Pollution (CRITICAL) Affected versions: < 0.4.0 Patched version: 0.4.0 From: yarn.lock → npm/[email protected] ℹ Read more on: This package | This alert | What is a critical CVE? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report