Open yafp opened 4 years ago
I’m pretty sure all of those prototype pollution and regex DOS vulns don’t actually apply to npx’s use case.
While you might be technically right - i still have to say that this is the first time i've seen an npm audit explode by adding a single additional dependency (and its dependencies) to one of my projects.
I’m pretty sure all of those prototype pollution and regex DOS vulns don’t actually apply to npx’s use case.
in general I doubt that this is the right way to argue about security issues ;)
META:
Generally I would question the lucidity of posting this kind of alert publicly instead of trying some other form of direct outreach, but seeing as the NPM org has not posted a security policy for this repo or mentioned security anywhere in its CONTRIBUTING.md
I totally understand why that was done. Thanks @yafp!
The hoek
issue is troubling, since the rest of the JS ecosystem has patched that (10?) months ago. Indeed, dependabot has PR's that have been open since November! Considering the superpowers that this little project has, I would not permit anyone on my teams to use it until all audit issues are resolved and a security policy is published.
Update
the npx update from 10.2.0 to 10.2.1 solved 3 of the reported issues (all from the category low) .
any new information here?
@sjt003
some general info in #30
The https://npm.im/libnpx package has since made a release 10.2.3 and I found no CHANGELOG fot that, while https://npm.im/npx does not show this version. So I guess there was an attempt to fix something 🎉
What / Why
I've added npx 10.2.0 today to my project (on an arch linux machine). After that i did execute
npm audit
to check for vulnerabilities and got the following output.or a bit more detailed:
Are there any plans to work on that?