0.2.16 — diff review from 0.2.15 only (current)
From zcash/rust-ecosystem copy of zcash/zcash. By str4d.
These reviews are from cargo-vet. To add your review, set up cargo-vet
and submit your URL to its registry.
0.2.16 — diff review from 0.2.15 only (current)
From zcash/rust-ecosystem copy of zcash/zcash. By str4d.
0.2.16 (current)
From kornelski/crev-proofs copy of salsa.debian.org. By Fabian Grünbichler.
Packaged for Debian (unstable). Changelog:
The current version of allocator-api2 is 0.2.16.
0.2.15 — diff review from 0.2.14 only (older version)
From zcash/rust-ecosystem copy of zcash/zcash. By str4d.
unsafe
code is moved without being altered.SliceExt
extension trait uses unsafe
methods Vec::set_len
and
core::ptr::copy_nonoverlapping
to initialize a Vec
efficiently. The safety
requirements appear to be satisfied.0.2.15 (older version)
From kornelski/crev-proofs copy of git.savannah.gnu.org.
Packaged for Guix (crates-io)
This crate will not introduce a serious security vulnerability to production software exposed to untrusted input. More…
This crate can be compiled, run, and tested on a local workstation or in controlled automation without surprising consequences. More…
cargo-vet does not verify reviewers' identity. You have to fully trust the source the audits are from.
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 allocator-api2
. Alternatively, you can download the tarball of allocator-api2 v0.2.16 or view the source online.
Change to
unsafe
block is to fix theDrop
impl ofBox
to drop its value.