1.0.130 — diff review from 1.0.129 only (older version)
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-macro is 1.0.135.
1.0.130 — diff review from 1.0.129 only (older version)
From google/supply-chain copy of chromium. Audited without comment by Adrian Taylor.
1.0.128 — diff review from 1.0.126 only (older version)
From zcash/rust-ecosystem copy of zcash/zcash. Audited without comment by str4d.
1.0.126 — diff review from 1.0.124 only (older version)
From google/supply-chain copy of chromium. Audited without comment by Lukasz Anforowicz.
1.0.124 — diff review from 1.0.123 only (older version)
From google/supply-chain copy of chromium. Audited without comment by Dustin J. Mitchell.
1.0.122 (older version)
From google/supply-chain copy of chromium. By Dana Jansens.
1.0.107 — diff review from 1.0.106 only (older version)
From google/supply-chain copy of chromium. Audited without comment by George Burgess IV.
1.0.107 (older version)
From kornelski/crev-proofs copy of git.savannah.gnu.org.
Packaged for Guix (crates-io)
1.0.91 — diff review from 1.0.83 only (older version)
From zcash/rust-ecosystem copy of zcash/zcash. Audited without comment by Jack Grigg.
1.0.87 (older version)
From kornelski/crev-proofs copy of salsa.debian.org.
Only in debcargo (unstable). Changelog:
1.0.79 — diff review from 1.0.78 only (older version)
From zcash/rust-ecosystem copy of zcash/zcash. Audited without comment by Kris Nuttycombe.
1.0.72 — diff review from 1.0.68 only (older version)
From zcash/rust-ecosystem copy of zcash/zcash. Audited without comment by Daira Emma Hopwood.
1.0.42 (older version)
From google/supply-chain copy of chromium. Audited without comment by Android Legacy.
cargo-vet does not verify reviewers' identity. You have to fully trust the source the audits are from.
This crate will not introduce a serious security vulnerability to production software exposed to untrusted input. More…
This crate can be compiled, run, and tested on a local workstation or in controlled automation without surprising consequences. More…
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.
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 implies crypto-safe
, but does not require expert review in order to
audit for.
May have been packaged automatically without a review
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-macro
. Alternatively, you can download the tarball of cxxbridge-macro v1.0.135 or view the source online.
no grep hits for cipher, crypto.
safe-to-deploy and ub-risk-2 are provided by exemption.