blocknative / web3-onboard

Client library to onboard users to web3 apps
https://onboard.blocknative.com/
MIT License
850 stars 504 forks source link

Import Inter font from new URL & bump packages that require common #2092

Closed Adamj1232 closed 7 months ago

Adamj1232 commented 7 months ago

Description

Import Inter font from new URL & bump packages that require common

Checklist

socket-security[bot] commented 7 months ago

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

Package New capabilities Transitives Size Publisher
npm/@esbuild-plugins/node-globals-polyfill@0.2.3 None 0 105 kB xmorse
npm/@esbuild-plugins/node-modules-polyfill@0.2.2 filesystem 0 71.3 kB xmorse
npm/@fontsource/fira-mono@4.5.10 None 0 1.02 MB lotusdevshack
npm/@jridgewell/sourcemap-codec@1.4.14 None 0 40 kB jridgewell
npm/@lit/reactive-element@1.6.1 None +1 800 kB lit-robot
npm/@rollup/plugin-commonjs@25.0.7 filesystem +2 247 kB shellscape
npm/@stablelib/random@1.0.2 None +3 157 kB dchest
npm/@sveltejs/adapter-auto@1.0.0-next.91 environment, filesystem, shell Transitive: eval +5 1.33 MB svelte-admin
npm/@sveltejs/kit@1.0.0-next.589 environment, eval, filesystem +4 1.32 MB svelte-admin
npm/@types/cookie@0.5.1 None 0 9.76 kB types
npm/@types/estree@1.0.0 None 0 25.7 kB types
npm/@typescript-eslint/eslint-plugin@5.49.0 Transitive: environment, filesystem +9 4.26 MB jameshenry
npm/@typescript-eslint/parser@5.49.0 Transitive: environment, filesystem +4 1.35 MB jameshenry
npm/@walletconnect/jsonrpc-provider@1.0.13 None +4 737 kB gancho_walletconnect
npm/@walletconnect/jsonrpc-types@1.0.3 None 0 74.1 kB gancho_walletconnect
npm/@walletconnect/jsonrpc-utils@1.0.8 None +2 419 kB gancho_walletconnect
npm/@walletconnect/safe-json@1.0.2 None 0 215 kB gancho_walletconnect
npm/@walletconnect/window-getters@1.0.1 None 0 218 kB bkrem
npm/@web3-onboard/injected-wallets@2.10.1 None 0 456 kB cmeisl
npm/@web3-onboard/walletconnect@2.3.9 Transitive: environment, eval, filesystem, network +69 23.2 MB cmeisl
npm/assert@2.1.0 None +1 104 kB ljharb
npm/browserify-aes@1.2.0 None +2 42.5 kB cwmma
npm/browserify-rsa@4.1.0 None +1 103 kB cwmma
npm/browserify-zlib@0.2.0 None 0 192 kB dignifiedquire
npm/buffer@6.0.3 None +1 101 kB feross
npm/call-bind@1.0.7 None 0 22.1 kB ljharb
npm/cipher-base@1.0.4 None 0 7.95 kB cwmma
npm/react-dom@18.2.0 environment +3 4.92 MB gnoff
npm/react@18.2.0 environment +1 322 kB gnoff
npm/regexp.prototype.flags@1.4.3 Transitive: eval +7 172 kB ljharb

🚮 Removed packages: npm/@solid-primitives/event-listener@2.3.0, npm/@solid-primitives/rootless@1.4.2, npm/@solid-primitives/utils@6.2.1, npm/bignumber.js@9.1.2, npm/normalize-path@3.0.0, npm/solid-devtools@0.27.7, npm/tsup-preset-solid@2.1.0, npm/tsup@7.2.0, npm/typescript@5.2.2

View full report↗︎

socket-security[bot] commented 7 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
Install scripts npm/@sveltejs/kit@1.0.0-next.589
  • Install script: postinstall
  • Source: node postinstall.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/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

  • @SocketSecurity ignore npm/@sveltejs/kit@1.0.0-next.589