[Snyk] Fix for 6 vulnerabilities

[snyk-io]

Snyk has created this PR to fix 6 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
	Information Exposure SNYK-JS-ELLIPTIC-8720086	251
	Improper Verification of Cryptographic Signature SNYK-JS-ELLIPTIC-7577916	224
	Improper Verification of Cryptographic Signature SNYK-JS-ELLIPTIC-7577917	224
	Improper Verification of Cryptographic Signature SNYK-JS-ELLIPTIC-7577918	224
	Denial of Service (DoS) SNYK-JS-WS-7266574	169
	Improper Verification of Cryptographic Signature SNYK-JS-ELLIPTIC-8172694	130

---

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:

🦉 Denial of Service (DoS)

Summary by Sourcery

Bug Fixes:

• Upgrade @ethersproject/experimental and @ethersproject/providers to address multiple critical and high severity vulnerabilities, including Information Exposure and Denial of Service (DoS).

[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.

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request updates @ethersproject/experimental and @ethersproject/providers in package.json to address 6 vulnerabilities.

Updated class diagram for package.json dependencies

classDiagram
  class PackageJson {
    -dependencies
    +updateDependencies()
  }

  PackageJson --|> EthersprojectExperimental : uses
  PackageJson --|> EthersprojectProviders : uses

  class EthersprojectExperimental {
    -version: string
    +getVersion(): string
  }
  note for EthersprojectExperimental "Updated from 5.5.0 to 5.8.0"

  class EthersprojectProviders {
    -version: string
    +getVersion(): string
  }
  note for EthersprojectProviders "Updated from 5.7.0 to 5.8.0"

Loading

File-Level Changes

Change	Details	Files
The pull request upgrades @ethersproject/experimental and @ethersproject/providers to address multiple vulnerabilities.	Upgraded @ethersproject/experimental from version 5.7.0 to 5.8.0. Upgraded @ethersproject/providers from version 5.7.0 to 5.8.0.	package.json

---

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. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the 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 exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!
• Generate a plan of action for an issue: Comment @sourcery-ai plan on
  an issue to generate a plan of action for it.

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.

[sourcery-ai]

We have skipped reviewing this pull request. Here's why:

• It seems to have been created by a bot (hey, snyk-io[bot]!). We assume it knows what it's doing!
• It seems to have been created by a bot ('[Snyk]' found in title). We assume it knows what it's doing!
• We don't review packaging changes - Let us know if you'd like us to change this.