Mentioning "0" would mean cargo would pick the latest dependency which is versioned "0.*" which would include versions incompatible with the one that this crate was written with and may break your create.
Thanks for the PR! While I usually recommend using the --locked flag with cargo install or using another package manager, I agree that dependencies can be scoped more tightly.
Mentioning "0" would mean cargo would pick the latest dependency which is versioned "0.*" which would include versions incompatible with the one that this crate was written with and may break your create.