0.2.0 (current)
From mozilla/supply-chain copy of hg. By Bobby Holley.
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.
- safe-to-deploy (implies safe-to-run)
-
This crate will not introduce a serious security vulnerability to production software exposed to untrusted input. More…
- safe-to-run
Implied by other criteria
This crate can be compiled, run, and tested on a local workstation or in controlled automation without surprising consequences. More…
Lib.rs has been able to verify that all files in the crate's tarball 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 guid_win. Alternatively, you can download the tarball of guid_win v0.2.0 or view the source online.
This crate has some unsafe code for the FFI bits, which I've reviewed carefully. It uses the deprecated mem::uninitialized(), which is generally sketchy. However the usage is pretty straightforward and while it's technically UB, it seems no more likely to lead to miscompilation than any other use of mem::uninitialized.