[Snyk] Security upgrade @oceanprotocol/lib from 3.0.0-next.5 to 5.0.0

[q1blue]

Snyk has created this PR to fix 1 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
	Use of a Cryptographic Primitive with a Risky Implementation SNYK-JS-ELLIPTIC-14908844	146

---

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.

[gemini-code-assist]

Summary of Changes

Hello @q1blue, 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 focuses on enhancing the project's security by upgrading a key dependency. The change specifically targets a known vulnerability, ensuring the application utilizes a more secure and up-to-date version of the library, thereby improving the overall security posture.

Highlights

• Dependency Upgrade: The @oceanprotocol/lib dependency has been upgraded from version 3.0.0-next.5 to 5.0.0.
• Security Fix: This upgrade addresses a 'Use of a Cryptographic Primitive with a Risky Implementation' vulnerability (SNYK-JS-ELLIPTIC-14908844) identified by Snyk.
• Automated PR: This pull request was automatically generated by Snyk to remediate the identified security vulnerability.

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, automatically generated by Snyk, upgrades @oceanprotocol/lib from 3.0.0-next.5 to 5.0.0 to fix a security vulnerability. This is a major version jump across two major versions, which introduces significant breaking changes. The application's extensive use of this library in hooks and utilities means that a thorough migration of the codebase is required to adapt to the new API of @oceanprotocol/lib v5. Furthermore, as noted in the pull request description, the yarn.lock file has not been updated, which is a critical issue that must be addressed manually before merging. Without these changes, the project will likely fail to build or run correctly.

[gemini-code-assist]

This upgrade from @oceanprotocol/lib v3 to v5 is a major breaking change that will require significant code modifications.

1. Breaking Changes:
A jump from v3 to v5 introduces numerous breaking changes. Based on the codebase, this will affect files such as:

• src/shared/@ocean/hooks/useOrder.ts
• src/shared/@ocean/hooks/useGetAccessDetails.ts
• src/shared/@ocean/utilities/ocean.ts
• and others that rely on @oceanprotocol/lib.

You will need to consult the @oceanprotocol/lib v4 and v5 migration guides and update all usages of the library accordingly. Without these updates, the application will not function correctly.

2. yarn.lock Not Updated:
As mentioned in the PR description, yarn.lock has not been updated. This is a critical step. After updating the code, you must run yarn install to generate the new lock file and commit it. Failure to do so will result in builds using the old, vulnerable version of the dependency, or failing altogether.

Given the automated nature of this PR, these manual steps are essential before merging.