25 critical, 22 high security vulnerabilities in the code (or referenced libs) #218
Description
Doing an npm install on the current (latest) state of the repo outputs the following colorful warning:
62 vulnerabilities (4 low, 10 moderate, 22 high, 26 critical)
Doing an npm audit fix reduces the number a little:
57 vulnerabilities (10 moderate, 22 high, 25 critical)
Shouldn't we warn the community to avoid running this code publicly until these KNOWN vulnerabilities are taken care of?