0.1.1 (older version)
From divviup/libprio-rs. By Ameer Ghani.
This review is from cargo-vet. To add your review, set up cargo-vet and submit your URL to its registry.
The current version of libbz2-rs-sys is 0.1.3.
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…
Crates in the crates.io registry are tarball snapshots uploaded by crates' publishers. The registry is not using crates' git repositories. There is absolutely no guarantee that the repository URL declared by the crate belongs to the crate, or that the code in the repository is the code inside the published tarball.
To review the actual code of the crate, it's best to use cargo crev open libbz2-rs-sys. Alternatively, you can download the tarball of libbz2-rs-sys v0.1.3 or view the source online.
libbz2-rs-sys mainly uses unsafe around the C FFI boundary, for libc interop, and for custom allocation support. Most end-user-facing decompression logic is in safe Rust. I have fuzzed and reviewed its code, and to the best of my ability I believe it's free of any serious security vulnerabilities.
libbz2-rs-sys only depends on the libc crate, which is widely used and maintained by the Rust project.