socket-security[bot]
commented
7 months ago New and removed dependencies detected. Learn more about Socket for GitHub ↗︎
🚮 Removed packages: npm/@npmcli/promise-spawn@6.0.2, npm/@octokit/types@9.3.2, npm/bl@4.1.0, npm/cli-spinners@2.6.1, npm/dotenv@16.3.1, npm/figures@3.2.0, npm/follow-redirects@1.15.2, npm/fs-minipass@3.0.2, npm/hosted-git-info@4.1.0, npm/is-core-module@2.12.1, npm/is-plain-obj@1.1.0, npm/jsonparse@1.3.1, npm/make-fetch-happen@11.1.1, npm/node-gyp-build@4.6.0, npm/node-machine-id@1.1.12, npm/normalize-package-data@3.0.3, npm/protocols@2.0.1, npm/sigstore@1.7.0, npm/tslib@2.6.0, npm/yargs-parser@20.2.4
This PR was automatically created by Snyk using the credentials of a real user.
Snyk has created this PR to fix one or more vulnerable packages in the `yarn` dependencies of this project.
#### Changes included in this PR - Changes to the following files to upgrade the vulnerable dependencies to a fixed version: - examples/web3-provider/package.json #### Note for [zero-installs](https://yarnpkg.com/features/zero-installs) users If you are using the Yarn feature [zero-installs](https://yarnpkg.com/features/zero-installs) that was introduced in Yarn V2, note that this PR does not update the `.yarn/cache/` directory meaning this code cannot be pulled and immediately developed on as one would expect for a zero-install project - you will need to run `yarn` to update the contents of the `./yarn/cache` directory. If you are not using zero-install you can ignore this as your flow should likely be unchanged.⚠️ Warning
``` Failed to update the yarn.lock, please update manually before merging. ```**Why?** Proof of Concept exploit, Recently disclosed, Has a fix available, CVSS 6.5 | Uncontrolled Resource Consumption ('Resource Exhaustion')
[SNYK-JS-TAR-6476909](https://snyk.io/vuln/SNYK-JS-TAR-6476909) | Yes | Proof of Concept (*) Note that the real score may have changed since the PR was raised. Check the changes in this PR to ensure they won't cause issues with your project. ------------ **Note:** *You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.* For more information: