0.3.0 (current) Thoroughness: Low Understanding: Low
by kornelski on 2024-10-24
This review is from Crev, a distributed system for code reviews. To add your review, set up cargo-crev.
This review is from cargo-vet. To add your review, set up cargo-vet and submit your URL to its registry.
* (all versions)
From mozilla/supply-chain copy of hg. By Jeff Muizelaar on 2020-11-05.
Maintained by the Graphics team at Mozilla in mozilla-central.
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, except Cargo.lock,
are in the crate's repository. 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 qcms. Alternatively, you can download the tarball of qcms v0.3.0 or view the source online.
It shows it's a copy-paste from a C codebase, and it's meant to be used from C as well. The main public API is still unsafe C FFI, with a thin Rust wrapper around it.