Update dependency-check to the latest version 🚀

[greenkeeper[bot]]

Version 3.0.0 of dependency-check was just published.

Dependency	dependency-check
Current Version	2.10.0
Type	devDependency

The version 3.0.0 is not covered by your current version range.

If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.

It might be worth looking into these changes and trying to get this project onto the latest version of dependency-check.

If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.

---

Commits

The new version differs by 10 commits.

• d0efa70 3.0.0
• bdbbfcf Update remaining dependencies
• 7bb339a Use latest version of read-package-json
• b7aef20 Enable strict mode
• ac7a817 Move from "var" to "const"/"let"
• e5fdc3a Use arrow functions
• 28502b5 Replace asyncMap with Promises
• 36b3d24 Ignore package manager lock files
• b8efac2 Require at least Node 6
• 5bf9ba6 Add new CLI option to readme

See the full diff

FAQ and help

There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).

---

Your Greenkeeper bot :palm_tree:

[coveralls]

Coverage remained the same at 98.75% when pulling 9c31ac955d02b54011d5c816fbe851c68c621911 on greenkeeper/dependency-check-3.0.0 into f57bb2ab38a857a85d27f2a056227f7966888cf0 on master.

[unional]

:tada: This PR is included in version 0.5.16 :tada:

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot :package::rocket: