Version Packages

[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@bitski/waas-react-sdk@1.0.4

Patch Changes

• #483 1f850b695e3288e15c1434180e6aedd9fa814a90 Thanks @RealAndyLawton! - Show nothing if Chain doesn't have known icon

[codesandbox]

Review or Edit in CodeSandbox

Open the branch in Web Editor • VS Code • Insiders

Open Preview

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/bitski@3.8.1	network	+4	1.66 MB	imthinhvu
npm/daisyui@2.52.0	None	+8	2.66 MB	saadeghi
npm/eslint-plugin-react-refresh@0.3.5	None	0	10.4 kB	arnaud-barre
npm/react-daisyui@3.1.2	None	+9	4.21 MB	benjitrosch
npm/viem@0.3.50	network Transitive: environment	+8	7.44 MB	jmoxey
npm/vite@4.5.2	environment, eval, filesystem, network, shell, unsafe	+23	211 MB	vitebot
npm/web3@1.9.0	Transitive: environment, eval, filesystem, network, shell, unsafe	+220	28.6 MB	jdevcs
npm/webpack-cli@3.3.12	environment, filesystem, shell, unsafe Transitive: eval, network	+220	12.5 MB	evilebottnawi
npm/webpack-dev-server@3.11.3	environment, filesystem, network Transitive: eval, shell, unsafe	+314	20.3 MB	evilebottnawi
npm/webpack@4.47.0	environment, filesystem, unsafe Transitive: eval, network, shell	+180	11.6 MB	thelarkinn

🚮 Removed packages: npm/@metamask/safe-event-emitter@2.0.0, npm/@openid/appauth@1.3.1, npm/@rollup/plugin-commonjs@23.0.7, npm/@rollup/plugin-node-resolve@15.2.3, npm/@statelyai/inspect@0.2.4, npm/@tanstack/eslint-plugin-query@5.20.1, npm/@tanstack/react-query@5.17.15, npm/@testing-library/dom@8.20.1, npm/@types/lodash.debounce@4.0.9, npm/@types/react-dom@18.2.18, npm/@types/react@18.2.48, npm/@typescript-eslint/eslint-plugin@6.19.0, npm/@typescript-eslint/parser@6.19.0, npm/@vitejs/plugin-react@4.2.1, npm/@wagmi/connectors@4.1.6, npm/@wagmi/core@2.3.1, npm/@xstate/react@4.1.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
Install scripts	npm/esbuild@0.18.20	Install script: postinstall Source: node install.js	examples/viem/package.json
Native code	npm/fsevents@1.2.13	Location: Package overview	examples/standalone/package.json
Install scripts	npm/fsevents@1.2.13	Install script: install Source: node install.js	examples/standalone/package.json
Native code	npm/secp256k1@4.0.3	Location: Package overview	examples/standalone/package.json
Install scripts	npm/web3-bzz@1.9.0	Install script: postinstall Source: echo "WARNING: the web3-bzz api will be deprecated in the next version"	examples/standalone/package.json
Install scripts	npm/web3-shh@1.9.0	Install script: postinstall Source: echo "WARNING: the web3-shh api will be deprecated in the next version"	examples/standalone/package.json
Install scripts	npm/es5-ext@0.10.64	Install script: postinstall Source: node -e "try{require('./_postinstall')}catch(e){}" || exit 0	examples/standalone/package.json
Protestware/Troll package	npm/es5-ext@0.10.64	Note: This package prints a protestware console message on install regarding Ukraine for users with Russian language locale	examples/standalone/package.json
Install scripts	npm/web3@1.9.0	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/ "	examples/standalone/package.json

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.

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 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/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/esbuild@0.18.20
• @SocketSecurity ignore npm/fsevents@1.2.13
• @SocketSecurity ignore npm/secp256k1@4.0.3
• @SocketSecurity ignore npm/web3-bzz@1.9.0
• @SocketSecurity ignore npm/web3-shh@1.9.0
• @SocketSecurity ignore npm/es5-ext@0.10.64
• @SocketSecurity ignore npm/web3@1.9.0