0.2.0 — diff review from 0.1.12 only (current)
From bytecodealliance/wasmtime. By Pat Hickey.
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 unicode-width is 0.2.0.
0.1.14 — diff review from 0.1.13 only (older version)
From google/supply-chain copy of chromium. Audited without comment by Lukasz Anforowicz.
0.1.12 — diff review from 0.1.11 only (older version)
From google/supply-chain copy of chromium. Audited without comment by Dana Jansens.
0.1.11 (older version)
From google/supply-chain copy of chromium. By Dana Jansens.
Reviewed in https://crrev.com/c/5171063
Previously reviewed during security review and the audit is grandparented in.
0.1.11 (older version)
From kornelski/crev-proofs copy of git.savannah.gnu.org.
Packaged for Guix (crates-io)
0.1.10 — diff review from 0.1.9 only (older version)
From mozilla/supply-chain copy of hg. Audited without comment by Mike Hommey.
0.1.9 (older version)
From google/supply-chain copy of chromium. Audited without comment by George Burgess IV.
0.1.8 (older version)
From google/supply-chain copy of chromium. Audited without comment by Android Legacy.
* (all versions)
From mozilla/supply-chain copy of hg. By Manish Goregaokar on 2019-12-05.
All code written or reviewed by Manish
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
-
This crate can be compiled, run, and tested on a local workstation or in controlled automation without surprising consequences. More…
- does-not-implement-crypto (implies crypto-safe)
-
Inspection reveals that the crate in question does not attempt to implement any cryptographic algorithms on its own.
Note that certification of this does not require an expert on all forms of cryptography: it's expected for crates we import to be "good enough" citizens, so they'll at least be forthcoming if they try to implement something cryptographic. When in doubt, please ask an expert.
- crypto-safe
Implied by other criteria
All crypto algorithms in this crate have been reviewed by a relevant expert.
Note: If a crate does not implement crypto, use
does-not-implement-crypto, which impliescrypto-safe, but does not require expert review in order to audit for.- unknown
-
May have been packaged automatically without a review
This review is from Crev, a distributed system for code reviews. To add your review, set up cargo-crev.
The current version of unicode-width is 0.2.0.
0.1.8 (older version) Thoroughness: High Understanding: High
by mgeisler on 2021-05-07
Nice crate with no unsafe code (uses deny(unsafe_code) to ensure
this). The data tables are generated automatically from the upstream
Unicode data using a Python script, which ensures that they’re
correct and easy to update when new Unicode versions are published.
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 unicode-width. Alternatively, you can download the tarball of unicode-width v0.2.0 or view the source online.
large changes to an auto-generated table file, which contains no unsafe code. code generator is checked-in and looks sensible.