Resolve security issues

lansingcodes / www

Events and resources for Lansing coders

https://www.lansing.codes

Other

7 stars 16 forks source link

Resolve security issues #130

Closed MegTheDev closed 3 years ago

MegTheDev commented 4 years ago

Update to latest versions of the following dependencies:

bl - https://github.com/lansingcodes/www/network/alert/package-lock.json/bl/open
yars-parser - https://github.com/lansingcodes/www/network/alert/package-lock.json/yargs-parser/open
http-proxy - https://github.com/lansingcodes/www/network/alert/package-lock.json/http-proxy/open
handlebars - https://github.com/lansingcodes/www/network/alert/package-lock.json/handlebars/open
lodash.merge - https://github.com/lansingcodes/www/network/alert/package-lock.json/lodash.mergewith/open
node-sass - https://github.com/lansingcodes/www/network/alert/package-lock.json/node-sass/open
lodash. defaultsdeep - https://github.com/lansingcodes/www/network/alert/package-lock.json/lodash.defaultsdeep/open
hapi - https://github.com/lansingcodes/www/network/alert/package-lock.json/hapi/open
ammo - https://github.com/lansingcodes/www/network/alert/package-lock.json/ammo/open
puppeteer - https://github.com/lansingcodes/www/network/alert/package-lock.json/puppeteer/open
bump lodash - https://github.com/lansingcodes/www/pull/128#event-3553996541

egillespie commented 4 years ago

Running npm audit will also show which dependencies have vulnerabilities, and you can try to run npm audit --fix to attempt to automatically update them as well.