New issue
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
chicken vs egg #92
Comments
You're definitely right. I will add that to the documentation. EDIT: I am not sure how to address this problem, it is definitely a chicken-egg problem. One strong consideration would be to reduce the number of dependencies used by |
One approach would be to do a global install as you mentioned but pipe the automatic audit response to something that can process the result; fail if |
Minimal testing, but I believe this will return an exit code of |
I guess another little test you can do without installing anything is:
|
Please tell me if I'm missing something but isn't
npm install --save-dev audit-ci
also an attack vector since it runsnpm install
and installs all packages? Isn't the whole point to avoid runningnpm install
until you verify packages are not compromised withnpm audit
?So running
npm install --save-dev audit-ci
is unsafe. The safest path to installing packages is something like (see below)?The text was updated successfully, but these errors were encountered: