Code reviews of the allocator-api2 crate // Lib.rs

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) safe-to-deploy

From zcash/rust-ecosystem copy of zcash/zcash. By str4d.

Change to unsafe block is to fix the Drop impl of Box to drop its value.

0.2.16 (current) safe-to-run, safe-to-deploy

From kornelski/crev-proofs copy of salsa.debian.org. By Fabian Grünbichler.

Packaged for Debian (unstable). Changelog:

Package allocator-api2 0.2.16 from crates.io using debcargo 2.6.0

The current version of allocator-api2 is 0.2.16.

0.2.15 — diff review from 0.2.14 only (older version) safe-to-deploy

From zcash/rust-ecosystem copy of zcash/zcash. By str4d.

Some existing unsafe code is moved without being altered.
The new 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) safe-to-run

From kornelski/crev-proofs copy of git.savannah.gnu.org.

Packaged for Guix (crates-io)

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

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.