Closed orsifacundo closed 7 months ago
adding the --quiet option to npm install seems to do the trick.. will further investigate.
hey @orsifacundo - this may be fixed with my recent merged PR #34 ; would you mind testing to see if this is still ongoing when using the latest main
branch content?
Totally, it's fixed now. Thanks @scrthq.. closing this issue.
When running the scan an output similar to this is being shown:
Even when using the --quiet (-q) option