0.7.0 — diff review from 0.6.1 only (older version)
From bytecodealliance/wasmtime. By Trevor Elliott.
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 regalloc2 is 0.11.1.
0.6.1 — diff review from 0.6.0 only (older version)
From bytecodealliance/wasmtime. By Chris Fallin.
Bytecode Alliance is the author of this crate.
0.4.2 — diff review from 0.4.1 only (older version)
From bytecodealliance/wasmtime. By Nick Fitzgerald.
Show review…
The Bytecode Alliance is the author of this crate.
0.3.2 — diff review from 0.3.1 only (older version)
From bytecodealliance/wasmtime. By Jamey Sharp.
Show review…
The Bytecode Alliance is the author of this crate.
0.3.1 (older version)
From fermyon/spin. By Radu Matei.
Show review…
The Bytecode Alliance is the author of this crate.
* (all versions)
From bytecodealliance/wasmtime. By Chris Fallin on 2021-12-03.
We (Bytecode Alliance) are the primary authors of regalloc2 and co-develop it with Cranelift/Wasmtime, with the same code-review, testing/fuzzing, and security standards.
* (all versions)
From bytecodealliance/wasmtime. By Trevor Elliott on 2022-11-29.
This is a Bytecode Alliance authored crate maintained in the regalloc2
repository of which I'm one of the maintainers and publishers for. I am employed
by a member of the Bytecode Alliance and plan to continue doing so and will
actively maintain this crate over time.
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…
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 regalloc2. Alternatively, you can download the tarball of regalloc2 v0.11.1 or view the source online.
The Bytecode Alliance is the author of this crate.