We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I have a project that depends on [email protected], which seems to be the latest version.
[email protected]
When running yarn audit, this error shows up since a few days ago:
yarn audit
┌───────────────┬──────────────────────────────────────────────────────────────┐ │ high │ netmask npm package vulnerable to octal input data │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ Package │ netmask │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ Patched in │ >=2.0.1 │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ Dependency of │ qiniu │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ Path │ qiniu > urllib > proxy-agent > pac-proxy-agent > │ │ │ pac-resolver > netmask │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ More info │ https://www.npmjs.com/advisories/1658 │ └───────────────┴──────────────────────────────────────────────────────────────┘ 1 vulnerabilities found - Packages audited: 901
https://www.npmjs.com/advisories/1658
It’d be great to see a new version of qiniu that depends on netmask@^2.0.1. Thank you!
qiniu
netmask@^2.0.1
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I have a project that depends on
[email protected]
, which seems to be the latest version.When running
yarn audit
, this error shows up since a few days ago:https://www.npmjs.com/advisories/1658
It’d be great to see a new version of
qiniu
that depends onnetmask@^2.0.1
. Thank you!The text was updated successfully, but these errors were encountered: