0.2.100 — diff review from 0.2.99 only (current)
From mozilla/supply-chain copy of mozilla/glean. Audited without comment by Lars Eggert.
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 wasm-bindgen is 0.2.100.
0.2.93 — diff review from 0.2.92 only (older version)
From google/supply-chain copy of google/rust-crate-audits. By Manish Goregaokar.
0.2.92 (older version)
From google/supply-chain copy of google/rust-crate-audits. By Matthew Maurer.
Reviewed in CL 643989424
0.2.91 (older version)
From kornelski/crev-proofs copy of git.savannah.gnu.org.
Packaged for Guix (crates-io)
0.2.87 (older version)
From kornelski/crev-proofs copy of salsa.debian.org.
Only in debcargo (unstable). Changelog:
- Team upload.
- Package wasm-bindgen 0.2.87 from crates.io using debcargo 2.6.0
cargo-vet does not verify reviewers' identity. You have to fully trust the source the audits are from.
- ub-risk-2 (implies ub-risk-3)
-
Negligible unsoundness or average soundness.
Full description of the audit criteria can be found at https://github.com/google/rust-crate-audits/blob/main/auditing_standards.md#ub-risk-2
- ub-risk-3 (implies ub-risk-4)
Implied by other criteria
Mild unsoundness or suboptimal soundness.
Full description of the audit criteria can be found at https://github.com/google/rust-crate-audits/blob/main/auditing_standards.md#ub-risk-3
- ub-risk-4
Implied by other criteria
Extreme unsoundness.
Full description of the audit criteria can be found at https://github.com/google/rust-crate-audits/blob/main/auditing_standards.md#ub-risk-4
- 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 wasm-bindgen. Alternatively, you can download the tarball of wasm-bindgen v0.2.100 or view the source online.
Reviewed in CL 695250202 Not much unsafe diff from last review