Skip to content

Conversation

@RealTschoegl
Copy link

snyk-top-banner

Snyk has created this PR to fix 1 vulnerabilities in the npm dependencies of this project.

Snyk changed the following file(s):

  • registry/s3-sync/package.json
  • registry/s3-sync/package-lock.json

Vulnerabilities that will be fixed with an upgrade:

Issue Score
medium severity Prototype Pollution
SNYK-JS-LODASH-15053838
  631  

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.
  • This PR was automatically created by Snyk using the credentials of a real user.

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:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic


Learn how to fix vulnerabilities with free interactive lessons:

🦉 Prototype Pollution

…on to reduce vulnerabilities

The following vulnerabilities are fixed with an upgrade:
- https://snyk.io/vuln/SNYK-JS-LODASH-15053838
@macroscopeapp
Copy link

macroscopeapp bot commented Jan 22, 2026

Update registry/s3-sync dependencies to remediate Snyk vulnerability by setting aws-sdk to ^2.1401.0 and s3-client to ^4.4.2

Bumps dependency ranges in registry/s3-sync and refreshes the lockfile to reflect new resolutions; see package.json and package-lock.json.

📍Where to Start

Start with dependency changes in package.json; then verify lock resolution in package-lock.json.


Macroscope summarized 75dc1fc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants