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 wasmparser is 0.221.2.

* (all versions) safe-to-deploy

From bytecodealliance/wasmtime. By Alex Crichton on 2020-07-13.

This is a Bytecode Alliance authored crate maintained in the wasm-tools repository 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.

* (all versions) safe-to-deploy

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.

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


These reviews are from Crev, a distributed system for code reviews. To add your review, set up cargo-crev.

The current version of wasmparser is 0.221.2.

0.15.3 (older version) Rating: Positive Thoroughness: Low Understanding: Medium

by MaulingMonkey on 2019-07-27

Looks great overall. I haven't double-checked any logic against WASM specs. I haven't verified that WASM validation is suitable to rely upon for JIT compilers or the like.

Detail

File Rating Notes
examples/dump.rs +1 io (safe)
examples/simple.rs +1 io (safe)
fuzz/* UNREVIEWED (excluded from crate)
src/lib.rs +1
src/limits.rs +1
src/parser.rs +1
src/tests.rs +1 io (safe)
src/validator.rs +1 check_utf8 could be mostly replaced with stdlib?
tests/*.wasm Unreviewed... nothing but WASM though, should be OK
.gitignore +1
.travis.yml +1
Cargo.toml +1
Cargo.toml.orig +1
check-rustfmt.sh +1 Globally overwrites rustfmt with specific version
format-all.sh +1
LICENSE +1 Apache 2.0
Readme.md +1
test-all.sh +1
Other Rating Notes
unsafe +1 No unsafe code.
fs +1 Examples and tests only, reasonably used.

0.15.2 (older version) Rating: Positive Thoroughness: Low Understanding: Medium

by MaulingMonkey on 2019-07-28

Show review…

Looks great overall. I haven't double-checked any logic against WASM specs. I haven't verified that WASM validation is suitable to rely upon for JIT compilers or the like.

Detail

File Rating Notes
examples/dump.rs +1 io (safe)
examples/simple.rs +1 io (safe)
fuzz/* UNREVIEWED (excluded from crate)
src/lib.rs +1
src/limits.rs +1
src/parser.rs +1
src/tests.rs +1 io (safe)
src/validator.rs +1 check_utf8 could be mostly replaced with stdlib?
tests/*.wasm Unreviewed... nothing but WASM though, should be OK
.gitignore +1
.travis.yml +1
Cargo.toml +1
Cargo.toml.orig +1
check-rustfmt.sh +1 Globally overwrites rustfmt with specific version
format-all.sh +1
LICENSE +1 Apache 2.0
Readme.md +1
test-all.sh +1
Other Rating Notes
unsafe +1 No unsafe code.
fs +1 Examples and tests only, reasonably used.

Lib.rs has been able to verify that all files in the crate's tarball, except Cargo.lock, 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 wasmparser. Alternatively, you can download the tarball of wasmparser v0.221.2 or view the source online.