These reviews are from cargo-vet. To add your review, set up cargo-vet and submit your URL to its registry.

3.0.2 — diff review from 2.2.0 only (current) safe-to-deploy

From bytecodealliance/wasmtime. By Alex Crichton.

This release brings a number of refactorings and new platforms to be supported in the crate. Lots of unsafe code because that's what the crate is fundamentally doing, managing virtual memory. That being said it's all largely the same as before where it's all as expected and the unsafe has to do with managing OS APIs.

The current version of Region is 3.0.2.

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


Lib.rs has been able to verify that all files in the crate's tarball are in the crate's repository with a git tag matching the version. 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 region. Alternatively, you can download the tarball of region v3.0.2 or view the source online.