Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Snyk] Upgrade node-fetch from 2.7.0 to 3.3.2 #4

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

rizwan-r-r
Copy link
Owner

This PR was automatically created by Snyk using the credentials of a real user.


![snyk-top-banner](https://github.com/andygongea/OWASP-Benchmark/assets/818805/c518c423-16fe-447e-b67f-ad5a49b5d123)

Snyk has created this PR to upgrade node-fetch from 2.7.0 to 3.3.2.

ℹ️ 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.


⚠️ Warning: This PR contains major version upgrade(s), and may be a breaking change.

  • The recommended version is 28 versions ahead of your current version.

  • The recommended version was released on a year ago.

Issues fixed by the recommended upgrade:

Issue Score Exploit Maturity
high severity Improper Control of Generation of Code ('Code Injection')
SNYK-JS-PUGCODEGEN-7086056
482 Proof of Concept
Release notes
Package name: node-fetch
  • 3.3.2 - 2023-07-25

    3.3.2 (2023-07-25)

    Bug Fixes

  • 3.3.1 - 2023-03-11

    3.3.1 (2023-03-11)

    Bug Fixes

    • release "Allow URL class object as an argument for fetch()" #1696 (#1716) (7b86e94)
  • 3.3.0 - 2022-11-10

    3.3.0 (2022-11-10)

    Features

  • 3.2.10 - 2022-07-31

    3.2.10 (2022-07-31)

    Bug Fixes

  • 3.2.9 - 2022-07-18

    3.2.9 (2022-07-18)

    Bug Fixes

    • Headers: don't forward secure headers on protocol change (#1599) (e87b093)
  • 3.2.8 - 2022-07-12
  • 3.2.7 - 2022-07-11
  • 3.2.6 - 2022-06-09
  • 3.2.5 - 2022-06-01
  • 3.2.4 - 2022-04-28
  • 3.2.3 - 2022-03-11
  • 3.2.2 - 2022-03-07
  • 3.2.1 - 2022-03-01
  • 3.2.0 - 2022-01-20
  • 3.1.1 - 2022-01-16
  • 3.1.0 - 2021-11-08
  • 3.0.0 - 2021-08-31
  • 3.0.0-beta.6-exportfix - 2020-05-25
  • 3.0.0-beta.10 - 2021-07-19
  • 3.0.0-beta.9 - 2020-09-05
  • 3.0.0-beta.8 - 2020-08-10
  • 3.0.0-beta.7 - 2020-06-11
  • 3.0.0-beta.6 - 2020-05-25
  • 3.0.0-beta.5 - 2020-04-22
  • 3.0.0-beta.4 - 2020-03-14
  • 3.0.0-beta.3 - 2020-03-13
  • 3.0.0-beta.2 - 2020-03-13
  • 3.0.0-beta.1 - 2020-03-13
  • 2.7.0 - 2023-08-23
from node-fetch GitHub release notes

Important

  • Warning: This PR contains a major version upgrade, and may be a breaking change.
  • 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:

Snyk has created this PR to upgrade node-fetch from 2.7.0 to 3.3.2.

See this package in npm:
node-fetch

See this project in Snyk:
https://app.snyk.io/org/rizwan-r-r/project/34a73f71-22c3-437c-8e03-b4d6c9ccdb25?utm_source=github&utm_medium=referral&page=upgrade-pr
Copy link

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

Package New capabilities Transitives Size Publisher
npm/[email protected] network 0 107 kB node-fetch-bot

View full report↗︎

@rizwan-r-r
Copy link
Owner Author

rizwan-r-r commented Jun 21, 2024

Deploy Preview for lucky-pavlova-6423b3 failed. Why did it fail? →

Name Link
🔨 Latest commit c743da2
🔍 Latest deploy log https://app.netlify.com/sites/lucky-pavlova-6423b3/deploys/66759c9101748600083e43d9

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.

"socket hang up" / ECONNRESET on consecutive requests with Node.js 19 and Node.js 20
2 participants