[Snyk] Security upgrade mocha from 6.2.3 to 11.0.1

[adamlaska]

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

Snyk changed the following file(s):

• contracts/extensions/package.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Missing Release of Resource after Effective Lifetime SNYK-JS-INFLIGHT-6095116	631

---

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:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/@0x/[email protected]	filesystem, shell Transitive: environment, network	+30	8.93 MB	tobernguyen
npm/@0x/[email protected]	Transitive: environment, eval, filesystem, network	+45	12.9 MB	dorothy-zbornak
npm/@0x/[email protected]	Transitive: environment, eval, filesystem, network	+48	20.3 MB	tobernguyen
npm/@0x/[email protected]	Transitive: environment, network	+21	8.63 MB	dorothy-zbornak
npm/@0x/[email protected]	Transitive: environment, eval, filesystem, network	+45	18.4 MB	tobernguyen
npm/@0x/[email protected]	None	0	613 kB	dorothy-zbornak
npm/@0x/[email protected]	Transitive: environment, network	+21	8.2 MB	dorothy-zbornak
npm/@0x/[email protected]	Transitive: environment, filesystem, network	+22	7.84 MB	tobernguyen
npm/@0x/[email protected]	environment Transitive: eval, filesystem, network	+71	75.1 MB	tobernguyen
npm/@0x/[email protected]	Transitive: environment, eval, filesystem, network	+45	17.5 MB	tobernguyen
npm/@0x/[email protected]	environment, filesystem Transitive: eval, network, shell	+92	27.7 MB	dorothy-zbornak
npm/@0x/[email protected]	Transitive: environment, eval, network	+27	9.18 MB	dorothy-zbornak
npm/@0x/[email protected]	environment, filesystem, network, shell Transitive: eval	+33	9.41 MB	tobernguyen
npm/@0x/[email protected]	filesystem Transitive: environment, network	+34	10.8 MB	fberger
npm/@0x/[email protected]	None	+1	758 kB	dekz
npm/@0x/[email protected]	None	+2	1.15 MB	dekz
npm/@0x/[email protected]	None	+4	3.19 MB	dekz
npm/@0x/[email protected]	network Transitive: environment	+22	8.38 MB	dorothy-zbornak
npm/@0x/[email protected]	Transitive: environment, eval, network	+26	8.98 MB	dorothy-zbornak
npm/[email protected]	None	+1	42.6 kB	chaijs
npm/[email protected]	None	+3	789 kB	chaijs
npm/[email protected]	None	0	20.3 kB	joshperry
npm/[email protected]	None	+2	1.11 MB	dekz

🚮 Removed packages: npm/[email protected]

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	CI
Critical CVE	npm/[email protected]	CVE: GHSA-67hx-6x53-jw92 Babel vulnerable to arbitrary code execution when compiling specifically crafted malicious code (CRITICAL) Affected versions: < 7.23.2 Patched version: No patched versions	Source	⚠︎
Git dependency	npm/[email protected]	Dependency: ethereumjs-abi@git+https://github.com/ethereumjs/ethereumjs-abi.git Location: Package overview	contracts/asset-proxy/package.json	⚠︎
Protestware or potentially unwanted behavior	npm/[email protected]	Note: The script attempts to run a local post-install script, which could potentially contain malicious code. The error handling suggests that it is designed to fail silently, which is a common tactic in malicious scripts.	Source	⚠︎
Protestware or potentially unwanted behavior	npm/[email protected]	Note: This package prints a protestware console message on install regarding Ukraine for users with Russian language locale	Source	⚠︎

View full report↗︎

Next steps

What is a critical CVE?

Contains a Critical Common Vulnerability and Exposure (CVE).

Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.

What are git dependencies?

Contains a dependency which resolves to a remote git URL. Dependencies fetched from git URLs are not immutable can be used to inject untrusted code or reduce the likelihood of a reproducible install.

Publish the git dependency to npm or a private package repository and consume it from there.

What is protestware?

This package is a joke, parody, or includes undocumented or hidden behavior unrelated to its primary function.

Consider that consuming this package may come along with functionality unrelated to its primary purpose.

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/[email protected] or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]