* (all versions)
From bytecodealliance/wasmtime. By Alex Crichton on 2020-12-11.
These reviews are from cargo-vet. To add your review, set up cargo-vet and submit your URL to its registry.
* (all versions)
From bytecodealliance/wasmtime. By Alex Crichton on 2023-01-01.
The Bytecode Alliance uses the wasmtime-publish crates.io account to automate
publication of this crate from CI. This repository requires all PRs are reviewed
by a Bytecode Alliance maintainer and it owned by the Bytecode Alliance itself.
* (all versions)
From bytecodealliance/wasmtime. Self-approved without comment by Nick Fitzgerald on 2019-03-16.
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. 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 wit-component. Alternatively, you can download the tarball of wit-component v0.220.0 or view the source online.
This is a Bytecode Alliance authored crate maintained in the
wasm-toolsrepository of which I'm one of the primary 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.