[Snyk] Fix for 22 vulnerabilities

[ryanhefner]

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

Snyk changed the following file(s):

• package.json
• package-lock.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Incomplete List of Disallowed Inputs SNYK-JS-BABELTRAVERSE-5962462	786
	Improper Verification of Cryptographic Signature SNYK-JS-ELLIPTIC-7577916	776
	Improper Verification of Cryptographic Signature SNYK-JS-ELLIPTIC-7577917	776
	Improper Verification of Cryptographic Signature SNYK-JS-ELLIPTIC-7577918	776
	Information Exposure SNYK-JS-SIMPLEGET-2361683	761
	Regular Expression Denial of Service (ReDoS) SNYK-JS-ANSIREGEX-1583908	696
	Uncontrolled resource consumption SNYK-JS-BRACES-6838727	696
	Regular Expression Denial of Service (ReDoS) SNYK-JS-MOMENT-2944238	696
	Regular Expression Denial of Service (ReDoS) SNYK-JS-SEMVER-3247795	696
	Code Injection SNYK-JS-LODASH-1040724	681
	Prototype Pollution SNYK-JS-JSON5-3182856	641
	Improper Verification of Cryptographic Signature SNYK-JS-BROWSERIFYSIGN-6037026	589
	Directory Traversal SNYK-JS-MOMENT-2440688	589
	Regular Expression Denial of Service (ReDoS) SNYK-JS-COLORSTRING-1082939	586
	Regular Expression Denial of Service (ReDoS) SNYK-JS-GLOBPARENT-1016905	586
	Regular Expression Denial of Service (ReDoS) SNYK-JS-LODASH-1018905	586
	Regular Expression Denial of Service (ReDoS) SNYK-JS-POSTCSS-1090595	586
	Regular Expression Denial of Service (ReDoS) SNYK-JS-POSTCSS-1255640	586
	Information Exposure SNYK-JS-NANOID-2332193	521
	Prototype Pollution SNYK-JS-MINIMIST-2429795	506
	Regular Expression Denial of Service (ReDoS) npm:debug:20170905	506
	Regular Expression Denial of Service (ReDoS) SNYK-JS-RAMDA-1582370	490

---

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:

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