Skip to content
New issue

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

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

Already on GitHub? # to your account

[Snyk] Upgrade nodemon from 2.0.15 to 2.0.22 #3

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

Conversation

ayushigoyal2840
Copy link
Owner

snyk-top-banner

Snyk has created this PR to upgrade nodemon from 2.0.15 to 2.0.22.

ℹ️ 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 7 versions ahead of your current version.

  • The recommended version was released on 2 years ago.

Issues fixed by the recommended upgrade:

Issue Score Exploit Maturity
medium severity Open Redirect
SNYK-JS-GOT-2932019
484 No Known Exploit
medium severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-HTTPCACHESEMANTICS-3248783
484 Proof of Concept
medium severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-MINIMATCH-3050818
484 No Known Exploit
low severity Prototype Pollution
SNYK-JS-MINIMIST-2429795
484 Proof of Concept
Release notes
Package name: nodemon from nodemon 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:

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Defaulting to ts-node is confusing when using ESM loaders Consider removing/replacing update-notifier
2 participants