[Snyk] Fix for 2 vulnerabilities #2
Open
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.
Snyk has created this PR to fix 2 vulnerabilities in the npm dependencies of this project.
Snyk changed the following file(s):
deps/npm/package.jsonVulnerabilities that will be fixed with an upgrade:
SNYK-JS-QS-3153490
SNYK-JS-SEMVER-3247795
Important
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 Poisoning
🦉 Regular Expression Denial of Service (ReDoS)
Description by Korbit AI
What change is being made?
Update dependencies in
package.jsonto fix vulnerabilities by upgrading versions ofinit-package-json,node-gyp,normalize-package-data,npm-package-arg,npm-registry-client,read-installed,read-package-json,realize-package-specifier, andrequest.Why are these changes being made?
These updates are necessary to address two identified vulnerabilities in the project, ensuring improved security and stability by using the latest versions of affected packages. The decision to update to these specific versions is based on compatibility and solving the stated security issues without introducing breaking changes.