devDeps: browserify@^16.5.0->^17.0.0

[legobeat]

No description provided.

[legobeat]

To see that this does not affect bundling:

• CI run based on ci: bundle as part of build-lint-test workflow #455 + babelify dependencies #454: https://github.com/MetaMask/web3-provider-engine/actions/runs/6555104638?pr=456

[socket-security]

Updated dependencies detected. Learn more about Socket for GitHub ↗︎

Packages	Version	New capabilities	Transitives	Size	Publisher
browserify	16.5.1...17.0.0	None	+11/-10	779 kB	goto-bus-stop

[socket-security]

👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎

This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored.

Ignoring: browser-resolve@2.0.0

Next steps

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of package-name@version specifiers. e.g. @SocketSecurity ignore foo@1.0.0 bar@* or ignore all packages with @SocketSecurity ignore-all

[legobeat]

@SocketSecurity ignore browser-resolve@2.0.0

new author ok