cargo install --force --features vendored-openssl cargo-outdated
Developing with Rust on macOS
Until you hit an openssl dependency.
Going the native way
Using native-tls abstracts the specific details away from the platforms and on desktop systems "just works" (usually)
For most applications this is a very good strategy to reduce the maintenance workload while remaining portable.
Going the vendored way
You can not rely on the platforms and distributions? You can ship your own and vendor everything.
With cargo-vendor you can automate the process on your machine and store all your dependencies in your git repository. You want to keep an eye out for all the licenses used if you are a business.
Going the homebrew way
Homebrew tries to turn your macOS into a more Unix/Linux environment. You get a package manager where you install openssl or anything else you need but now you have to maintain two systems on the same machine.