Closed lucalovin closed 3 years ago
I experienced the same thing. It seems to work (i.e. table is populated) when using npm 6.14.10 but not after upgrading to npm 7.7.6
@lucalovin Are you on NPM 7? If so, that is likely the issue. npm-audit-report
doesn't yet support NPM 7 due to breaking changes in the report JSON structure (see #43).
Oh, I understand. Now I have to figure out why npm audit doesn't work at all with npm 6 (i get the ENOAUDIT error, "audit Your configured registry (https://registry.npmjs.org/) may not support audit requests, or the audit endpoint may be temporarily unavailable."). Tried different solutions but nothing worked. Did you maybe experience this before and found a solution?
Thanks for your answer!
@lucalovin I am working on NPM 7 support so it should be available Soonâ„¢
I've not seen NPM 6 throw that error with the default registry. That is strange. I would recommend searching Stack Overflow for that issue.
Closing this issue since it is already being worked on in #43.
Sure, thanks!
Hi,
I followed the steps and tried to run npm-audit-html on some repositories but every time I get "No data available in table", even though I can see that there are vulnerabilities. Any idea why this happens and how can I fix the issue?
Thanks!