[Snyk] Upgrade solidity-rlp from 2.0.1 to 2.0.8

[OKEAMAH]

Snyk has created this PR to upgrade solidity-rlp from 2.0.1 to 2.0.8.

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

• The recommended version was released on a year ago.

Release notes

Package name: solidity-rlp

• 2.0.8 - 2023-05-12
  

  Changed

  • Support any patch version of v0.8
• 2.0.7 - 2023-02-14
  

  Changed

  • Extended Solidity support to v0.8.18
• 2.0.6 - 2022-12-14
  

  Changed

  • Extended Solidity support to v0.8.17
• 2.0.5 - 2021-05-12
  

  Changed

  • Save gas when copying memory that's a multiple of 32 bytes.
• 2.0.4 - 2021-04-03
  

  Added

  • rlpBytesKeccak256(RLPItem) returns keccak256 hash of RLP encoded bytes.
  • payloadKeccak256(RLPItem) returns keccak256 hash of the item payload.
  • payloadLocation(RLPItem) (uint memPtr, uint len) returns the memory pointer and byte length of
    the data payload.
• 2.0.3 - 2020-12-01
  

  2.0.3

  Added

  • support for solidity 0.6.x
• 2.0.2 - 2020-08-25
  

  2.0.2

  Changed

  • toBoolean(RLPItem) will return false for the rlp encoded string, "0x80". This is because common
    rlp encoding libraries will encode "0" as "0x80".
• 2.0.1 - 2019-08-22
  

  2.0.1

  Added

  • iterator(RLPItem) returns an iterator object over an rlp encoded list
  • hasNext(Iterator) returns a boolean if the iterator has an item to iterate on next
  • next(Iterator) returns (RLPItem) returns an RLPItem of the next item up for iteration

from solidity-rlp GitHub release notes

---

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.

---

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

[sourcery-ai]

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

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

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/[email protected]	None	0	52.1 kB	hamdiallam

🚮 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	CI
Install scripts	npm/[email protected]	Install script: preinstall Source: node index.js	🚫

View full report↗︎

Next steps

What is an install script?

Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts.

Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead.

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]