Good Old Snyk

[knoxcard]

✗ Low severity vulnerability found on hoek@4.2.0

• desc: Prototype Pollution
• info: https://snyk.io/vuln/npm:hoek:20180212
• from: node_services@1.0.0 > npm@5.7.1 > libcipm@1.3.3 > npm-lifecycle@2.0.0 > node-gyp@3.6.2 > request@2.83.0 > hawk@6.0.2 > hoek@4.2.0 Your dependencies are out of date, otherwise you would be using a newer hoek than hoek@4.2.0. Try deleting node_modules, reinstalling and running snyk test again. If the problem persists, one of your dependencies may be bundling outdated modules.

✗ Low severity vulnerability found on hoek@4.2.0

• desc: Prototype Pollution
• info: https://snyk.io/vuln/npm:hoek:20180212
• from: node_services@1.0.0 > npm@5.7.1 > libcipm@1.3.3 > npm-lifecycle@2.0.0 > node-gyp@3.6.2 > request@2.83.0 > hawk@6.0.2 > boom@4.3.1 > hoek@4.2.0 Your dependencies are out of date, otherwise you would be using a newer hoek than hoek@4.2.0. Try deleting node_modules, reinstalling and running snyk test again. If the problem persists, one of your dependencies may be bundling outdated modules.

✗ Low severity vulnerability found on hoek@4.2.0

• desc: Prototype Pollution
• info: https://snyk.io/vuln/npm:hoek:20180212
• from: node_services@1.0.0 > npm@5.7.1 > libcipm@1.3.3 > npm-lifecycle@2.0.0 > node-gyp@3.6.2 > request@2.83.0 > hawk@6.0.2 > sntp@2.0.2 > hoek@4.2.0 Your dependencies are out of date, otherwise you would be using a newer hoek than hoek@4.2.0. Try deleting node_modules, reinstalling and running snyk test again. If the problem persists, one of your dependencies may be bundling outdated modules.

✗ Low severity vulnerability found on hoek@4.2.0

• desc: Prototype Pollution
• info: https://snyk.io/vuln/npm:hoek:20180212
• from: node_services@1.0.0 > npm@5.7.1 > libcipm@1.3.3 > npm-lifecycle@2.0.0 > node-gyp@3.6.2 > request@2.83.0 > hawk@6.0.2 > cryptiles@3.1.2 > boom@5.2.0 > hoek@4.2.0 Your dependencies are out of date, otherwise you would be using a newer hoek than hoek@4.2.0. Try deleting node_modules, reinstalling and running snyk test again. If the problem persists, one of your dependencies may be bundling outdated modules.

Tested 1135 dependencies for known vulnerabilities, found 1 vulnerability, 4 vulnerable paths.

[mtharrison]

You need to follow the instructions in the link you posted and update to 4.2.1.

[lock[bot]]

This thread has been automatically locked due to inactivity. Please open a new issue for related bugs or questions following the new issue template instructions.