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.

The current version of allocator-api2 is 0.3.0.

0.2.20 — diff review from 0.2.18 only (older version) safe-to-deploy

From bytecodealliance/wasmtime. By Chris Fallin.

The changes appear to be reasonable updates from Rust's stdlib imported into allocator-api2's copy of this code.

0.2.18 (older version) safe-to-deploy

From mozilla/supply-chain copy of hg. Audited without comment by Nicolas Silva.

0.2.18 — diff review from 0.2.16 only (older version) safe-to-deploy

From zcash/rust-ecosystem copy of zcash/zcash. Audited without comment by Daira-Emma Hopwood.

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

From zcash/rust-ecosystem copy of zcash/zcash. By Jack Grigg.

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

0.2.16 (older version) unknown

From kornelski/crev-proofs copy of salsa.debian.org.

Only in debcargo (unstable). Changelog:

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

0.2.15 (older version) unknown

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

Packaged for Guix (crates-io)

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…

unknown

May have been packaged automatically without a review

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.3.0 or view the source online.