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
NVD has issued https://nvd.nist.gov/vuln/detail/CVE-2017-16028 which captures one of browser-syncs' sub-dependencies: randomatic (1.1.7).
$ npm ls randomatic my-package@0.1.0 /Users/jevon/workspace/my-package └─┬ browser-sync@2.26.0 └─┬ micromatch@2.3.11 └─┬ braces@1.8.5 └─┬ expand-range@1.8.2 └─┬ fill-range@2.2.3 └── randomatic@1.1.7
I'm not sure if you need to update your dependencies, or if the CVE itself needs to be fixed, but as it stands I think any project using browser-sync will fail npm audit.
See also: jonschlinkert/randomatic#15
The text was updated successfully, but these errors were encountered:
9f3fea4
@soundasleep hopefully 2.26.2 solves this (although I couldn't actually get npm audit to fail for me)
npm audit
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
NVD has issued https://nvd.nist.gov/vuln/detail/CVE-2017-16028 which captures one of browser-syncs' sub-dependencies: randomatic (1.1.7).
I'm not sure if you need to update your dependencies, or if the CVE itself needs to be fixed, but as it stands I think any project using browser-sync will fail npm audit.
See also: jonschlinkert/randomatic#15
The text was updated successfully, but these errors were encountered: