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
Hi, I found that [email protected] uses [email protected] which will introduce a vulnerable library [email protected]. But this vulnerability has already been fixed in the master branch of npm-check.
Could you publish a version of npm-check to fix related issue?
The version of got library that npm-check depends now.
Thank you for your continuous efforts to maintain the npm-check package. It's a crucial tool in our development workflow, and we appreciate your efforts in keeping it up-to-date.
We noticed that renovate[bot] has made a number of updates to the dependencies of npm-check. However, because there hasn't been a new release of npm-check for some time, these changes are not reflected in the npmjs registry. This has caused some difficulties in our development environment when fetching the dependencies via npm install.
To solve this problem, we kindly request for a new release of npm-check on the npmjs registry to include the updated dependencies.
Thank you for your understanding and support. We are looking forward to the new release.
Best Regards,
Charles Cai
CharlesCai01
changed the title
package.json Mismatch between master branch and tag v6.0.1
Request for New Release of npm-check
Sep 6, 2023
Hi, I found that [email protected] uses [email protected] which will introduce a vulnerable library [email protected]. But this vulnerability has already been fixed in the master branch of npm-check.
Could you publish a version of npm-check to fix related issue?
The version of got library that npm-check depends now.
The package.json of Master branch
The package.json of v6.0.1 tag
The below is information about the vulnerability that [email protected] has.
BDSA-2022-3763 3.8 Low
CVE-2022-33987 5.3 Medium https://nvd.nist.gov/vuln/detail/CVE-2022-33987
The text was updated successfully, but these errors were encountered: