socket-security[bot]
commented
6 months ago New and removed dependencies detected. Learn more about Socket for GitHub ↗︎
| Package | New capabilities | Transitives | Size | Publisher |
|---|---|---|---|---|
| npm/@aws-sdk/types@3.465.0 | None | +1 |
275 kB | aws-sdk-bot |
| npm/@openzeppelin/defender-base-client@1.54.0-rc.0 | Transitive: network | +8 |
2.24 MB | collins-oz |
| npm/@openzeppelin/defender-relay-client@1.54.0-rc.0 | Transitive: network | +37 |
5.98 MB | collins-oz |
| npm/@smithy/types@2.7.0 | None | 0 |
234 kB | smithy-team |
| npm/amazon-cognito-identity-js@6.3.7 | network | +6 |
2.21 MB | aws-amplify-ops |
| npm/follow-redirects@1.15.1 | network | 0 |
27.7 kB | rubenverborgh |
🚮 Removed packages: npm/buffer@5.7.1, npm/eventemitter3@4.0.7, npm/retry@0.12.0
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/upgrade-contract/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 | Information Exposure
[SNYK-JS-FOLLOWREDIRECTS-6444610](https://snyk.io/vuln/SNYK-JS-FOLLOWREDIRECTS-6444610) | 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: