[Snyk] Upgrade node-fetch from 2.7.0 to 3.3.2 #2
Conversation
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/okeamah/project/621ee7c4-0dc5-4a40-aee3-a63976a31e8e?utm_source=github&utm_medium=referral&page=upgrade-pr
![sourcery-ai[bot]](https://avatars.githubusercontent.com/in/48477?s=60&v=4){kind=small}
There was a problem hiding this comment.
We have skipped reviewing this pull request. Here's why:
- It seems to have been created by a bot ('[Snyk]' found in title). We assume it knows what it's doing!
- We don't review packaging changes - Let us know if you'd like us to change this.
|
🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎ To accept the risk, merge this PR and you will not be notified again.
Next stepsWhat is an install script?Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts. Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead. Take a deeper look at the dependencyTake a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev. Remove the packageIf you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency. Mark a package as acceptable riskTo ignore an alert, reply with a comment starting with
|
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.
The recommended version is 28 versions ahead of your current version.
The recommended version was released on a year ago.
Release notes
Package name: node-fetch
-
3.3.2 - 2023-07-25
- Remove the default connection close header. (#1736) (8b3320d), closes #1735 #1473
-
3.3.1 - 2023-03-11
- release "Allow URL class object as an argument for fetch()" #1696 (#1716) (7b86e94)
-
3.3.0 - 2022-11-10
- add static Response.json (#1670) (55a4870)
-
3.2.10 - 2022-07-31
- ReDoS referrer (#1611) (2880238)
-
3.2.9 - 2022-07-18
- 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 notes3.3.2 (2023-07-25)
Bug Fixes
3.3.1 (2023-03-11)
Bug Fixes
3.3.0 (2022-11-10)
Features
3.2.10 (2022-07-31)
Bug Fixes
3.2.9 (2022-07-18)
Bug Fixes
Important
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: