[Snyk] Upgrade @openzeppelin/contracts from 5.2.0 to 5.5.0

[Dargon789]

Snyk has created this PR to upgrade @openzeppelin/contracts from 5.2.0 to 5.5.0.

ℹ️ 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 8 versions ahead of your current version.

• The recommended version was released 22 days ago.

Issues fixed by the recommended upgrade:

	Issue	Score	Exploit Maturity
	Out-of-bounds Read SNYK-JS-OPENZEPPELINCONTRACTS-10773735	559	No Known Exploit

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• This PR was automatically created by Snyk using the credentials of a real user.
• Max score is 1000. Note that the real score may have changed since the PR was raised.

---

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
• 📜 Customise PR templates
• 🛠 Adjust upgrade PR settings
• 🔕 Ignore this dependency or unsubscribe from future upgrade PRs

[snyk-io]

⚠️ Snyk checks are incomplete.

Status	Scanner	Critical	High	Medium	Low	Total (0)
⚠️	Open Source Security	0	0	0	0	See details

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[gemini-code-assist]

Summary of Changes

Hello @Dargon789, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request, automatically generated by Snyk, aims to enhance the project's security and maintainability by updating the @openzeppelin/contracts dependency to its latest stable version, 5.5.0. This critical upgrade resolves a known 'Out-of-bounds Read' vulnerability. The process also triggered a cascade of updates across various development dependencies, particularly within the ESLint ecosystem, ensuring all packages are aligned with their most recent and secure versions.

Highlights

• Dependency Upgrade: The primary change involves upgrading the @openzeppelin/contracts dependency from version 5.2.0 to 5.5.0.
• Security Fix: This upgrade addresses a medium-severity 'Out-of-bounds Read' vulnerability (SNYK-JS-OPENZEPPELINCONTRACTS-10773735), enhancing the security posture of the project.
• Transitive Dependency Updates: The update to @openzeppelin/contracts and the general dependency refresh have led to several other package updates in yarn.lock, including major version bumps for ESLint and its related ecosystem packages like @eslint/eslintrc, @eslint/js, espree, eslint-scope, and eslint-visitor-keys.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request upgrades @openzeppelin/contracts from 5.2.0 to 5.5.0 to address a security vulnerability. While this is a necessary update, the fix is incomplete because a transitive dependency, @1inch/solidity-utils, still relies on a vulnerable version of @openzeppelin/contracts. I've suggested adding a resolutions block to package.json to ensure all dependencies use the patched version, fully mitigating the vulnerability. Additionally, this PR includes a major version upgrade for ESLint and its related packages, which may introduce new linting errors. Please ensure your CI checks pass.

[gemini-code-assist]

While upgrading @openzeppelin/contracts is correct, this change doesn't resolve the vulnerability completely. The dependency @1inch/solidity-utils still uses a vulnerable version (5.1.0), as seen in the yarn.lock file. This means your project is still exposed to the vulnerability this PR aims to fix.

To ensure the vulnerability is patched across the entire dependency tree, you should add a resolutions field to your package.json. This will force all instances of @openzeppelin/contracts to use the specified secure version.

Please add the following block to your package.json (for example, after the scripts block):

  "resolutions": {
    "@openzeppelin/contracts": "5.5.0"
  }

After adding this, you'll need to run yarn install to update the yarn.lock file accordingly.