Skip to content

[Snyk] Upgrade proxy from 2.1.1 to 2.2.0#5

Open
snyk-io[bot] wants to merge 1 commit intomainfrom
snyk-upgrade-5bcc52722b951c5c80e020fb4959e603
Open

[Snyk] Upgrade proxy from 2.1.1 to 2.2.0#5
snyk-io[bot] wants to merge 1 commit intomainfrom
snyk-upgrade-5bcc52722b951c5c80e020fb4959e603

Conversation

@snyk-io
Copy link
Copy Markdown

@snyk-io snyk-io Bot commented Jan 3, 2025

snyk-top-banner

Snyk has created this PR to upgrade proxy from 2.1.1 to 2.2.0.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 1 version ahead of your current version.

  • The recommended version was released 6 months ago.

Issues fixed by the recommended upgrade:

Issue Score Exploit Maturity
low severity Information Exposure
SNYK-JS-UNDICI-5962466
83 No Known Exploit
low severity Permissive Cross-domain Policy with Untrusted Domains
SNYK-JS-UNDICI-6252336
83 No Known Exploit
low severity Improper Access Control
SNYK-JS-UNDICI-6564963
83 No Known Exploit
low severity Improper Authorization
SNYK-JS-UNDICI-6564964
83 No Known Exploit
Release notes
Package name: proxy from proxy GitHub release notes

Important

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

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

@semanticdiff-com
Copy link
Copy Markdown

semanticdiff-com Bot commented Jan 3, 2025

Review changes with  SemanticDiff

Changed Files
File Status
  packages/http-client/package.json  0% smaller

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.

0 participants