-
Notifications
You must be signed in to change notification settings - Fork 331
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature Request: Update to the minimum version with no security vulnerabilities of a certain severity #1475
Comments
Hi, thanks for the suggestion. I have a question. When you say "next available version," what did you have in mind? Since the default behavior of npm-check-updates is to update the dependency to the latest version, there is no "next" version. Are you using other options to limit the version number? |
Hi For example, assuming my application.. Using the --min-secure, should suggest me to update to 1.0.19 instead of 1.3.0. To give you context, in a "SDL Secure Development Lifecycle", during each sprint we ask teams to work on a small security item, to review, fix, prevent and so on. |
I see! And if |
Very good question. |
So I think in that case what you're looking for is the maximum secure version, rather than the minimum. I'm not sure how to access the security vulnerabilities, but it sounds like a good suggestion. |
It would be nice to have an option like --min-secure "severity", to allow a safer and quicker upgrade if security issues are found within the dependencies.
For example if I specify --min-secure high, the tool should list the next available version to upgrade to, which is not affected by any issue with severity high or critical.
The text was updated successfully, but these errors were encountered: