Closed MrBenJ closed 6 years ago
I think this issue isn’t really a problem, as this is just stuff user for development. It’s not like we’re running a server that could crash (in which case this would be a problem).
I do think that other people will see this warning and take it too literally though, so I’m fine with upgrading to ava@next 👍
I totally agree with you on that @wooorm - The reason I'm bringing this up is that Github and npm both show big warnings on my repos that use your project. They look a little like this:
While it's alarming, it really isn't that bad of an issue, since like you said, Alex isn't running a server or similar.
I'll go ahead and fix this up for you. PR incoming before end of day today :) (USA time)
Hello!
I found the root cause of the npm audit
issue. It's here:
https://github.com/alessioalex/git-spawned-stream/pull/5
I submitted a PR to that project as well. Those tests are passing right now and hopefully we can get this all taken care of :D.
As a quick side note, there's this great free tool I use to keep dependencies up to date called Greenkeeper.
Thanks again! Appreciate you maintaining this awesome project :)
Issue fixed in git-spawned-stream
, published version 1.0.1
to npm already.
Perfect! OK if I close this?
fine by me, sure!
Subject of the issue
There's a low severity vulnerability issue with the
debug
package used in babel 6 and Ava for tests.Your environment
Steps to reproduce
Start a new project with
npm init
Installalex
withnpm install alex
Notice thenpm audit
security vulnerability appear.Expected behaviour
There should be no security vulnerabilities when installing
alex
Actual behaviour
There is a low severity security vulnerability.
Offer of assistance
I can refactor the tests and upgrade
ava
toava@next
which uses Babel 7, and remove the old dependency of debug v2 to remove this vulnerability.If this offer of assistance sounds good, go ahead and assign this issue to me and I'll take care of it right away!
Thank you for creating a wonderful project to contribute to!