moonbeam-foundation / xcm-sdk

The Moonbeam XCM SDK enables developers to easily transfer assets between chains, either between parachains or between a parachain and the relay chain, within the Polkadot/Kusama ecosystem. With the SDK, you don't need to worry about determining the multilocation of the origin or destination assets or which extrinsics are used on which networks to
https://moonbeam-foundation.github.io/xcm-sdk/latest/
MIT License
14 stars 9 forks source link

Viem V2 / Ethers V6 and update deps #178

Closed mmaurello closed 8 months ago

mmaurello commented 9 months ago

Description

Update dependencies

Checklist

changeset-bot[bot] commented 9 months ago

🦋 Changeset detected

Latest commit: 88d81ccf808cdce5f591bb68fc4365cd762ca788

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 5 packages | Name | Type | | ----------------------------- | ----- | | @moonbeam-network/xcm-config | Major | | @moonbeam-network/xcm-utils | Major | | @moonbeam-network/xcm-sdk | Major | | @moonbeam-network/xcm-builder | Major | | @moonbeam-network/xcm-types | Major |

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

socket-security[bot] commented 8 months ago

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

Package New capabilities Transitives Size Publisher
npm/@changesets/cli@2.27.1 environment, filesystem, shell Transitive: eval, unsafe +249 24.1 MB changesets-release-bot
npm/@polkadot/api-augment@10.11.2 Transitive: environment, filesystem, network +55 62.1 MB polkadotjs
npm/@polkadot/api@10.11.2 Transitive: environment, filesystem, network +58 64.1 MB polkadotjs
npm/@polkadot/types@10.11.2 None +28 19.8 MB polkadotjs
npm/@polkadot/util-crypto@12.6.2 None +22 10.6 MB polkadotjs
npm/@polkadot/util@12.6.2 None +9 4.82 MB polkadotjs
npm/@types/big.js@6.2.2 None 0 18.5 kB types
npm/@types/jest@29.5.11 Transitive: environment, filesystem, unsafe +44 5.61 MB types
npm/@typescript-eslint/eslint-plugin@6.21.0 Transitive: environment, eval, filesystem, shell, unsafe +121 48.8 MB jameshenry
npm/@typescript-eslint/parser@6.21.0 Transitive: environment, eval, filesystem, shell, unsafe +110 44 MB jameshenry
npm/bun@1.0.21 environment, filesystem, network, shell +6 422 MB robobun
npm/eslint-config-airbnb-typescript@17.1.0 Transitive: environment, eval, filesystem, shell, unsafe +203 54.3 MB iamturns
npm/eslint-config-prettier@9.1.0 Transitive: environment, eval, filesystem, shell, unsafe +92 10.6 MB lydell
npm/eslint-plugin-import@2.29.1 filesystem, unsafe Transitive: environment, eval, shell +169 15.9 MB ljharb
npm/eslint-plugin-jest@27.6.1 filesystem Transitive: environment, eval, network, shell, unsafe +383 74.9 MB simenb
npm/eslint-plugin-prettier@5.1.3 Transitive: environment, eval, filesystem, shell, unsafe +99 19.3 MB jounqin
npm/eslint@8.56.0 environment, filesystem Transitive: eval, shell, unsafe +91 10.6 MB eslintbot
npm/ethers@6.11.0 network Transitive: environment, filesystem +8 18.3 MB ricmoo
npm/glob@10.3.10 Transitive: environment, filesystem, shell +23 2.42 MB isaacs
npm/husky@9.0.10 environment, filesystem, shell 0 3.61 kB typicode
npm/jest@29.7.0 Transitive: environment, eval, filesystem, network, shell, unsafe +291 56.6 MB simenb
npm/lint-staged@15.2.2 Transitive: environment, filesystem, shell +52 2.47 MB okonet
npm/lru-cache@7.18.3 None 0 134 kB isaacs
npm/prettier@3.2.5 environment, filesystem, unsafe 0 8.39 MB prettier-bot
npm/ts-jest@29.1.2 environment, filesystem, unsafe Transitive: eval, network, shell +295 57.1 MB kul
npm/ts-node@10.9.2 environment, filesystem, unsafe +19 38.1 MB blakeembrey
npm/tsup@8.0.1 environment, eval, filesystem Transitive: network, shell, unsafe +158 304 MB egoist
npm/turbo@1.12.3 None +6 117 MB turbobot
npm/typescript@5.3.3 None 0 32 MB typescript-bot
npm/viem@2.7.8 network Transitive: environment, filesystem +15 45.8 MB jmoxey

🚮 Removed packages: npm/@changesets/cli@2.26.2, npm/@polkadot/api-augment@10.10.1, npm/@polkadot/api@10.10.1, npm/@polkadot/types@10.10.1, npm/@polkadot/util-crypto@12.5.1, npm/@polkadot/util@12.5.1, npm/@types/big.js@6.1.6, npm/@types/jest@29.5.3, npm/@typescript-eslint/eslint-plugin@5.59.9, npm/@typescript-eslint/parser@5.59.9, npm/bun@1.0.20, npm/eslint-config-airbnb-typescript@17.0.0, npm/eslint-config-prettier@8.8.0, npm/eslint-plugin-import@2.27.5, npm/eslint-plugin-jest@27.2.1, npm/eslint-plugin-prettier@4.2.1, npm/eslint@8.42.0, npm/ethers@5.7.2, npm/glob@10.3.3, npm/husky@8.0.3, npm/jest@29.6.1, npm/lint-staged@13.2.3, npm/lru-cache@7.17.0, npm/ts-jest@29.1.0, npm/tsup@6.7.0, npm/turbo@1.10.2, npm/type-fest@3.8.0, npm/typescript@5.1.3, npm/viem@1.10.3

View full report↗︎

socket-security[bot] commented 8 months ago

🚨 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 NoteSource
Native code npm/bufferutil@4.0.8

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.

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/bufferutil@4.0.8