1.0.130 — diff review from 1.0.129 only (current)
From google/supply-chain copy of chromium. Audited without comment by Adrian Taylor.
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 cxxbridge-cmd is 1.0.130.
1.0.129 — diff review from 1.0.128 only (older version)
From google/supply-chain copy of chromium. Audited without comment by Liza Burakova.
1.0.128 — diff review from 1.0.126 only (older version)
From google/supply-chain copy of chromium. Audited without comment by Dana Jansens.
1.0.126 — diff review from 1.0.124 only (older version)
From google/supply-chain copy of chromium. By Lukasz Anforowicz.
1.0.124 — diff review from 1.0.123 only (older version)
From google/supply-chain copy of chromium. By Dustin J. Mitchell.
No changes except to dependencies
1.0.110 (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.
cargo-vet does not verify reviewers' identity. You have to fully trust the source the audits are from.
- 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.
Lib.rs has been able to verify that all files in the crate's tarball, except Cargo.lock,
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 cxxbridge-cmd. Alternatively, you can download the tarball of cxxbridge-cmd v1.0.130 or view the source online.
Only minor changes:
let Some(foo) = ... else { ... }pattern in a few places.rust::Slice.