Without the --locked option and without dependencies properly specified in the hook, a new version release of a dependency can cause the hook that previously worked to suddenly stop working. Therefore, I propose adding an option to use --locked, as propsed in pre-commit/pre-commit#3162 .

Alternatively, as proposed in #681, supporting cargo-binstall would also resolve this issue for users with limited security concerns.