[Snyk] Upgrade ethers from 6.4.0 to 6.9.2

[naiba4]

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

Snyk has created this PR to upgrade ethers from 6.4.0 to 6.9.2.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

---

• The recommended version is 19 versions ahead of your current version.
• The recommended version was released 22 days ago, on 2024-01-03.

Release notes

Package name: ethers

• 6.9.2 - 2024-01-03
  
  • Fix Base58 padding for string representation of binary data (#4527; ccac24a).
• 6.9.1 - 2023-12-20
  
  • Fix uncatchable issue when sending transactions over JSON-RPC and provide some retry-recovery for missing v (#4513; 1802215).
• 6.9.0 - 2023-11-27
  
  • Use provider-specified suggested priority fee when available, otherwise fallback onto existing logic of 1 gwei (#4463; f8f11c7).
  • Add auto-detected static network support to providers and allow customizing socket provider options (#4199, #4418, #4441; 4681b83).
  • Added Base network to AlchemyProvider (#4384; 9e74d14).
  • Fixed ParamType formatting causing bad tuple full and minimal ABI output (#4329, #4479; 2b67488).
  • Adjust for provider config weight when kicking off a request in FallbackProvider (#4298; da34e35).
  • More robust FallbackProvider broadcast (#4186, #4297, #4442; e2485b8).
  • Added safe and finalized provider events (#3921; a92766e).
• 6.8.1 - 2023-11-01
  
  • Fixed typo in error description when converting values to arrays (#4427, #4446; 8fed2f8).
  • Fix invalid token nonpayable being included in formatted constructor (#4412; 2e0bd90).
  • Add ENS support for Sepolia (#4422; 1da50ae).
• 6.8.0 - 2023-10-11
  
  • Replicated former ENS normalize behaviour for empty strings and update namehash testcases (125ff11).
  • Initial shortMessage support for errors (#4241; d6a8c14).
  • Fixed resolving ENS addresses used as from parameters (#3961; 2616f4c).
  • Merge: 9a4b753 0c9c23b Merge branch 'v5.8-progress' (cd5f0fe).
  • Allow more loose input format for RLP encoder (#4402; 9a4b753).
  • Update to latest noble crypto libraries (#3975; b27faa0).
  • More robust configuration options for FetchRequest getUrl functions (#4353; 9541f2f).
  • Ignore blockTag when calling Etherscan if it is the default block tag (dcea9b3).
• 6.7.1 - 2023-08-15
  
  • Prevent destroyed providers from emitting network detection errors (7d41730).
  • Fix VSCode reported lint issues (#4153, #4156, #4158, #4159; 4eb84da, 203dfc3).
  • Add gasPrice to Polygon feeData for type 0 and type 1 legacy transactions (#4315; 0df3ab9).
• 6.7.0 - 2023-08-03
  
  • Fixed receipt wait not throwing on reverted transactions (25fef4f).
  • Added custom priority fee to Optimism chain (via telegram) (ff80b04).
  • Add context to Logs that fail decoding due to ABI issues to help debugging (f3c46f2).
  • Added new exports for FallbackProviderOptions and FetchUrlFeeDataNetworkPlugin (#2828, #4160; b1dbbb0).
  • Allow overriding pollingInterval in JsonRpcProvider constructor (via discord) (f42f258).
  • Fixed FallbackProvider priority sorting (#4150; 78538eb).
  • Added linea network to InfuraProvider and Network (#4184, #4190; d3e5e2c).
  • Added whitelist support to getDefaultProvider (82bb936).
  • Add Polygon RPC endpoints to the default provider (#3689; 23704a9).
  • Added customizable quorum to FallbackProvider (#4160; 8f0a509).
  • Added basic Gas Station support via a NetworkPlugin (#2828; 229145d).
  • Add BNB URLs to EtherscanProvider networks (ec39abe).
  • Added tests for JSON format (#4248; ba36079).
  • Use empty string for unnamed parameters in JSON output instead of undefined (#4248; 8c2652c).
  • Return undefined for Contract properties that do not exist instead of throwing an error (#4266; 5bf7b34).
• 6.6.7 - 2023-07-28
  
  • Prevent malformed logs from preventing other logs being decoded (#4275; 0dca645).
  • Allow visibility on human-readable constructors (via telegram) (3a52201).
• 6.6.6 - 2023-07-28
  
  • Better error message when passing invalid overrides object into a contract deployment (#4182; aa2ea3d).
• 6.6.5 - 2023-07-24
  
  • Reflect symbols in the Contract Proxy to target (#4048; ac2f5e5).
  • Allow arrays of address for indexed filter topics (#4259; 93af87c).
  • Fixed filter encoding for bytesX (#4244; fa3a883).
  • Fix JSON formatting for tuple arrays (#4237; a8bc49b).
  • Better error messages when parsing fragment strings (#4246; e36b6c3).
  • Include the missing fragment key and args when no matching Contract method or event is present (#3809; 450a176).
  • Prevent a single malformed event from preventing other Contract logs; reported on Discord (b1375f4).
• 6.6.4 - 2023-07-16
• 6.6.3 - 2023-07-12
• 6.6.2 - 2023-06-28
• 6.6.1 - 2023-06-23
• 6.6.0 - 2023-06-14
• 6.5.1 - 2023-06-08
• 6.5.0 - 2023-06-07
• 6.4.2 - 2023-06-06
• 6.4.1 - 2023-06-02
• 6.4.0 - 2023-05-20

from ethers GitHub release notes

Commit messages

Package name: ethers

• ccac24a Fix Base58 padding for string representation of binary data (#4527).
• f6d155c admin: update dist files
• 1802215 Fix uncatchable issue when sending transactions over JSON-RPC and provide some retry-recovery for missing v (#4513).
• 6ee1a5f docs: Fixed some grammar in getting-started (#4486, #4487, #4488)
• 98910ba admin: update changelog after build-clean
• d60dfc1 admin: updated dist files
• f8f11c7 Use provider-specified suggested priority fee when available, otherwise fallback onto existing logic of 1 gwei (#4463).
• 4681b83 Add auto-detected static network support to providers and allow customizing socket provider options (#4199, #4418, #4441).
• 9e74d14 Added Base network to AlchemyProvider (#4384).
• 2b67488 Fixed ParamType formatting causing bad tuple full and minimal ABI output (#4329, #4479).
• da34e35 Account for provider config weight when kicking off a request in FallbackProvider (#4298).
• e2485b8 More robust FallbackProvider broadcast (#4186, #4297, #4442).
• 93fb138 admin: style fix (#4356)
• 944cbbc tests: bumped Node versions for testing (#4451)
• a92766e Added safe and finalized provider events (#3921).
• cf00331 admin: updated dist files
• ee79d7d admin: added diff scripts for build page
• aff7add docs: fixed typo in jsdocs for Wallet.createRandom (#4461)
• 3931528 docs: updated the readme with more recent URLs and info
• 1c71ec6 docs: fixed jsdocs for signMessage (#4314)
• 1d9c019 docs: removed Pocket from list of community resources (#4345)
• 168518f docs: fixed typos in Fetch jsdocs (#4355)
• e9fac92 docs: fixed typo in ENS cookbook (#4379)
• 238f4f6 docs: fixed typo from copy-paste ENS cookbook example (#4382)

Compare

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

[pull-request-quantifier-deprecated]

This PR has 2 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

---

Quantification details

Label      : Extra Small
Size       : +1 -1
Percentile : 0.8%

Total files changed: 2

Change summary by file extension:
.json : +1 -1

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

• Fast and predictable releases to production:
  • Optimal size changes are more likely to be reviewed faster with fewer
    iterations.
  • Similarity in low PR complexity drives similar review times.
• Review quality is likely higher as complexity is lower:
  • Bugs are more likely to be detected.
  • Code inconsistencies are more likely to be detected.
• Knowledge sharing is improved within the participants:
  • Small portions can be assimilated better.
• Better engineering practices are exercised:
  • Solving big problems by dividing them in well contained, smaller problems.
  • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

• Use the PullRequestQuantifier to quantify your PR accurately
  • Create a context profile for your repo using the context generator
  • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
  • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
  • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
• Change your engineering behaviors
  • For PRs that fall outside of the desired spectrum, review the details and check if:
    • Your PR could be split in smaller, self-contained PRs instead
    • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

• One line was added: +1 -0
• One line was deleted: +0 -1
• One line was modified: +1 -1 (git diff doesn't know about modified, it will
  interpret that line like one addition plus one deletion)
• Change percentiles: Change characteristics (addition, deletion, modification)
  of this PR in relation to all other PRs within the repository.

---

Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.

[guardrails]

⚠️ We detected 7 security issues in this pull request:

Vulnerable Libraries (7)

Severity	Details
Medium	pkg:npm/eslint@8.29.0 (t) upgrade to: > 8.29.0
Medium	pkg:npm/@typescript-eslint/parser@5.46.1 (t) upgrade to: > 5.46.1
High	pkg:npm/vuepress@2.0.0-beta.59 (t) upgrade to: > 2.0.0-beta.59
High	pkg:npm/vuepress-plugin-md-enhance@2.0.0-beta.143 (t) upgrade to: > 2.0.0-beta.143
High	pkg:npm/docsearch.js@2.6.3 (t) upgrade to: > 2.6.3
Medium	pkg:npm/@typescript-eslint/eslint-plugin@5.46.1 (t) upgrade to: > 5.46.1
Medium	pkg:npm/eslint-plugin-vue@9.8.0 (t) upgrade to: > 9.8.0

More info on how to fix Vulnerable Libraries in JavaScript.

---

👉 Go to the dashboard for detailed results.

📥 Happy? Share your feedback with us.

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/@sentry/browser@7.95.0	network	+7	9.77 MB	sentry-bot
npm/ethers@6.9.2	network	+7	19.3 MB	ricmoo

🚮 Removed packages: npm/@sentry/browser@7.36.0, npm/ethers@6.4.0

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
Network access	npm/@sentry/utils@7.95.0	Module: globalThis["fetch"] Location: Package overview	theme/package.json
Unpublished package	npm/@sentry-internal/tracing@7.95.0	Version: Invalid Date	theme/package.json
Unpublished package	npm/@sentry-internal/feedback@7.95.0	Version: Invalid Date	theme/package.json
Unpublished package	npm/@sentry-internal/replay-canvas@7.95.0	Version: Invalid Date	theme/package.json
Unpublished package	npm/@sentry/replay@7.95.0	Version: Invalid Date	theme/package.json

View full report↗︎

Next steps

What is network access?

This module accesses the network.

Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use.

What are unpublished packages?

Package version was not found on the registry. It may exist on a different registry and need to be configured to pull from that registry.

Packages can be removed from the registry by manually un-publishing, a security issue removal, or may simply never have been published to the registry. Reliance on these packages will cause problem when they are not found.

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/@sentry/utils@7.95.0
• @SocketSecurity ignore npm/@sentry-internal/tracing@7.95.0
• @SocketSecurity ignore npm/@sentry-internal/feedback@7.95.0
• @SocketSecurity ignore npm/@sentry-internal/replay-canvas@7.95.0
• @SocketSecurity ignore npm/@sentry/replay@7.95.0