updated the transaction error

[samkeleN]

No description provided.

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/@celo/[email protected]	None	0	3.93 MB	app-tooling
npm/@celo/[email protected]	eval Transitive: environment, filesystem, network, shell, unsafe	+416	61 MB	app-tooling
npm/[email protected]	None	0	32.4 MB	typescript-bot

🚮 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	Source	CI
Native code	npm/[email protected]	Location: Package overview	package-lock.json package.json
Native code	npm/[email protected]	Location: Package overview	package-lock.json package.json
Native code	npm/[email protected]	Location: Package overview	package-lock.json package.json
Native code	npm/[email protected]	Location: Package overview	package-lock.json package.json
Install scripts	npm/[email protected]	Install script: postinstall Source: echo "Web3.js 4.x alpha has been released for early testing and feedback. Checkout doc at https://docs.web3js.org/ "	package-lock.json package.json
Install scripts	npm/[email protected]	Install script: postinstall Source: echo "WARNING: the web3-bzz api will be deprecated in the next version"	package-lock.json package.json
Install scripts	npm/[email protected]	Install script: postinstall Source: echo "WARNING: the web3-shh api will be deprecated in the next version"	package-lock.json package.json
Native code	npm/[email protected]	Location: Package overview	package-lock.json package.json
Install scripts	npm/[email protected]	Install script: postinstall Source: echo "Web3.js 4.x alpha has been released for early testing and feedback. Checkout doc at https://docs.web3js.org/ "	package-lock.json package.json
Install scripts	npm/[email protected]	Install script: postinstall Source: echo "WARNING: the web3-bzz api will be deprecated in the next version"	package-lock.json package.json
Install scripts	npm/[email protected]	Install script: postinstall Source: echo "WARNING: the web3-shh api will be deprecated in the next version"	package-lock.json package.json
Install scripts	npm/[email protected]	Install script: postinstall Source: node -e "try{require('./_postinstall')}catch(e){}" || exit 0	package-lock.json package.json
Protestware/Troll package	npm/[email protected]	Note: This package prints a protestware console message on install regarding Ukraine for users with Russian language locale	package-lock.json package.json

View full report↗︎

Next steps

What's wrong with native code?

Contains native code which could be a vector to obscure malicious code, and generally decrease the likelihood of reproducible or reliable installs.

Ensure that native code bindings are expected. Consumers may consider pure JS and functionally similar alternatives to avoid the challenges and risks associated with native code bindings.

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.

What is protestware?

This package is a joke, parody, or includes undocumented or hidden behavior unrelated to its primary function.

Consider that consuming this package my come along with functionality unrelated to its primary purpose.

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]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]