Update Node Fetch #99
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
👋 Hello there! Welcome. Please fill out the following template before submitting your contribution for review and double check the contribution guidelines.
Description of the Change
This PR is to fix a vulnerability from Node Fetch package, on updating that dependency on a patch version.
Is this change addressing any open issues?
No.
Is this change backwards compatible for existing users?
No. This change just fix a security breach from Node Fetch, as can be read on CVE-2022-0235, CWE-200, and SNYK-JS-NODEFETCH-2342118.
So, this PR update only a patch version from a dependency of this package.
Does this change require additional Twitter API knowledge?
No.