This review is from cargo-vet. To add your review, set up cargo-vet and submit your URL to its registry.

cargo-vet does not verify reviewers' identity. You have to fully trust the source the audits are from.

unknown

May have been packaged automatically without a review


These reviews are from Crev, a distributed system for code reviews. To add your review, set up cargo-crev.

The current version of remove_dir_all is 0.8.2.

0.5.3 (older version) Rating: Positive Thoroughness: Low Understanding: Low

by Minoru on 2021-03-04

I'm not a Windows programmer; I merely took a peek to see if the crate is blatantly malicious, and it looks like it isn't.

The code is well-commented. Uses unsafe sparingly, just to call WinAPI — no high-performance tricks. Some comments refer to alignment issues, which shows the amount of thought that went into the code; nice.

0.5.3 (older version) Rating: Positive Thoroughness: Low Understanding: Medium

Approved without comment by NinProf on 2021-01-27

0.5.2 (older version) Rating: Neutral Thoroughness: Low Understanding: Low

by kornelski on 2019-07-22


Lib.rs has been able to verify that all files in the crate's tarball, except Cargo.lock, are in the crate's repository with a git tag matching the version. Please note that this check is still in beta, and absence of this confirmation does not mean that the files don't match.

Crates in the crates.io registry are tarball snapshots uploaded by crates' publishers. The registry is not using crates' git repositories, so there is a possibility that published crates have a misleading repository URL, or contain different code from the code in the repository.

To review the actual code of the crate, it's best to use cargo crev open remove_dir_all. Alternatively, you can download the tarball of remove_dir_all v0.8.2 or view the source online.