The node/crypto.verify type signature does not match the official documentation, defining the return type as a Buffer instead of a boolean: https://nodejs.org/docs/latest-v12.x/api/crypto.html#crypto_crypto_verify_algorithm_data_key_signature
This API did not exist in versions of Node <12.0

• Use a meaningful title for the pull request. Include the name of the package modified.
• Test the change in your own code. (Compile and run.)
• Add or edit tests to reflect the change. (Run with npm test.)
• Follow the advice from the readme.
• Avoid common mistakes.
• Run npm run lint package-name (or tsc if no tslint.json is present).

If changing an existing definition:

• Provide a URL to documentation or source code which provides context for the suggested changes: https://nodejs.org/docs/latest-v12.x/api/crypto.html#crypto_crypto_verify_algorithm_data_key_signature
• If this PR brings the type definitions up to date with a new version of the JS library, update the version number in the header.
• If you are making substantial changes, consider adding a tslint.json containing { "extends": "dtslint/dt.json" }. If for reason the any rule need to be disabled, disable it for that line using // tslint:disable-next-line [ruleName] and not for whole package so that the need for disabling can be reviewed.