[Snyk] Security upgrade sao from 0.22.17 to 1.0.0

[titanism]

This PR was automatically created by Snyk using the credentials of a real user.

Snyk has created this PR to fix one or more vulnerable packages in the `yarn` dependencies of this project.

Changes included in this PR

• Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
  • package.json
  • yarn.lock

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.

Vulnerabilities that will be fixed

With an upgrade:

Severity	Priority Score (*)	Issue	Breaking Change	Exploit Maturity
	661/1000 Why? Recently disclosed, Has a fix available, CVSS 7.5	Uncontrolled resource consumption SNYK-JS-BRACES-6838727	Yes	No Known Exploit
	661/1000 Why? Recently disclosed, Has a fix available, CVSS 7.5	Inefficient Regular Expression Complexity SNYK-JS-MICROMATCH-6838728	Yes	No Known Exploit

(*) Note that the real score may have changed since the PR was raised.

Check the changes in this PR to ensure they won't cause issues with your project.

---

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

🛠 Adjust project settings

📚 Read more about Snyk's upgrade and patch logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Uncontrolled resource consumption

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/bn.js@5.1.3	None	0	99.8 kB	fanatid
npm/call-bind@1.0.2	None	+1	39.9 kB	ljharb
npm/decompress-tar@4.1.1	None	+2	25.1 kB	kevva
npm/extend-shallow@3.0.2	None	+3	28.9 kB	phated
npm/get-intrinsic@1.1.1	eval	+3	75.9 kB	ljharb
npm/is-callable@1.2.3	None	0	21.1 kB	ljharb
npm/nlcst-normalize@2.1.5	None	+1	13 kB	wooorm
npm/parse-asn1@5.1.6	None	+3	176 kB	cwmma
npm/quotation@1.1.3	None	0	4.9 kB	wooorm
npm/regex-not@1.0.2	None	0	8.46 kB	jonschlinkert
npm/regexp-tree@0.1.23	None	0	313 kB	dmitrysoshnikov

🚮 Removed packages: npm/rimraf@3.0.2, npm/ripemd160@2.0.2, npm/safe-buffer@5.1.2, npm/safer-buffer@2.1.2, npm/sao@0.22.17, npm/semver@7.3.4, npm/sha.js@2.4.11, npm/signal-exit@3.0.3, npm/source-map@0.5.7, npm/speakingurl@14.0.1, npm/string-width@4.2.0, npm/string_decoder@1.3.0, npm/strip-json-comments@3.1.1, npm/superb@4.0.0, npm/supports-color@7.2.0, npm/through@2.3.8, npm/trim-off-newlines@1.0.1, npm/tslib@1.14.1, npm/type-check@0.4.0, npm/type-fest@0.8.1, npm/unified@9.2.0, npm/unist-util-generated@1.1.6, npm/unist-util-position@3.1.0, npm/update-notifier@5.1.0, npm/uppercamelcase@3.0.0, npm/util-deprecate@1.0.2, npm/uuid@3.4.0, npm/vfile-location@3.2.0, npm/write-file-atomic@3.0.3, npm/xo@0.37.1, npm/xtend@4.0.2, npm/yargs-parser@20.2.4, npm/yargs@15.4.1

View full report↗︎

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source
Install scripts	npm/ejs@2.7.4	Install script: postinstall Source: node ./postinstall.js	orphan: npm/ejs@2.7.4

View full report↗︎

Next steps

What is an install script?

Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts.

Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead.

Take a deeper look at the dependency

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 support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/ejs@2.7.4