build fails: StdFilePusher vs FilePusher

[iconoclasthero]

error[E0432]: unresolved import `fast_down::file::FilePusher`
  --> /home/$USER/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/fast-down-cli-2.7.8/src/commands/download.rs:15:5
   |
15 |     file::FilePusher,
   |     ^^^^^^^^^^^^^^^^ no `FilePusher` in `file`
   |
help: a similar name exists in the module
   |
15 |     file::StdFilePusher,
   |           +++

For more information about this error, try `rustc --explain E0432`.
error: could not compile `fast-down-cli` (bin "fd") due to 1 previous error
error: failed to compile `fast-down-cli v2.7.8`, intermediate artifacts can be found at `/tmp/cargo-installAr2fnb`.
To reuse those artifacts with a future compilation, set the environment variable `CARGO_BUILD_BUILD_DIR` to that path.

google said this was because download.rs wasn't properly updated; dunno, i don't write in rust.

[iconoclasthero]

"Just use the bash download script and install it that way."
No, I do not want to have random stuff installed on my system from random scripts that offer no tracking and no way to update them. While it would be preferable if it was in a repo (e.g., AUR) then my package manager would see it, at least if I use cargo, cargo has a record that it installed it.... i.e., using cargo install gives you a much saner paper trail than blindly running someone's installation script.

[iconoclasthero]

Changing lines 259 and 15 in download.rs to StdFilePusher allowed the install to proceed, however, when I went to download something and used fastdown -f <url> -o cover.jpg I got cover (2).jpg instead of overwriting the existing cover.jpg.

Options:
  -f, --force
          Force overwrite existing file

If that's not the purpose of -f, what is the functionality of force and/or how do I overwrite an existing file with a cli flag? (I.e., the reason I am looking to replace axel.)