You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For version 1.1.0 dependency is upon semver ~7.0.0, which is vulnerable to Regular Expression Denial of Service the patch is in 7.5.4, which not seems supported for the above version.
Issue Title: Dependency on outdated semver version (~7.0.0)
Description:
The simple-update-notifier package depends on semver@~7.0.0, but I need to use [email protected] to address certain vulnerabilities. Can this dependency be updated to allow for a more recent version?
Steps to Reproduce:
Install simple-update-notifier.
Run npm install and check the version of semver being used.
Expected Behavior:
The package should allow using a newer version of semver, such as 7.5.4.
The text was updated successfully, but these errors were encountered:
Hi @shandli123 , is there a reason why you can't use version 2.0.0 of this package which patches this semver version?
Unfortunately from #19 it looks like bumping the semver version caused nodemon to crash which was the original user of this package. They have since updated to 2.0.0 to fix the issue, but I'm worried that changing this may fix security warnings, but will cause people using the old nodemon to crash.
For version 1.1.0 dependency is upon semver ~7.0.0, which is vulnerable to Regular Expression Denial of Service the patch is in 7.5.4, which not seems supported for the above version.
Issue Title: Dependency on outdated semver version (~7.0.0)
Description:
The
simple-update-notifier
package depends onsemver@~7.0.0
, but I need to use[email protected]
to address certain vulnerabilities. Can this dependency be updated to allow for a more recent version?Steps to Reproduce:
simple-update-notifier
.npm install
and check the version ofsemver
being used.Expected Behavior:
The package should allow using a newer version of
semver
, such as7.5.4
.The text was updated successfully, but these errors were encountered: