1.0.131 (older version)
From google/supply-chain copy of chromium. By Lukasz Anforowicz.
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-flags is 1.0.134.
1.0.131 (older version)
From google/supply-chain copy of chromium. By Lukasz Anforowicz.
1.0.130 (older version)
From google/supply-chain copy of chromium. Audited without comment by Adrian Taylor.
1.0.129 (older version)
From google/supply-chain copy of chromium. Audited without comment by Liza Burakova.
1.0.128 (older version)
From google/supply-chain copy of chromium. Audited without comment by Dana Jansens.
1.0.124 (older version)
From google/supply-chain copy of chromium. By Dustin J. Mitchell.
No changes in this delta
1.0.122 — diff review from 1.0.121 only (older version)
From zcash/rust-ecosystem copy of zcash/zcash. Audited without comment by str4d.
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.
1.0.107 (older version)
From google/supply-chain copy of chromium. By George Burgess IV.
rg -i unsafe
resulted in zero hits for this package.
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.
Packaged for Debian (stable). Changelog:
1.0.79 — diff review from 1.0.78 only (older version)
From zcash/rust-ecosystem copy of zcash/zcash. By Kris Nuttycombe.
This is exclusively an update to the cxxbridge
dependency version.
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.
No unsafe code.
Full description of the audit criteria can be found at https://github.com/google/rust-crate-audits/blob/main/auditing_standards.md#ub-risk-0
Excellent 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-1
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
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
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
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 cxxbridge-flags
. Alternatively, you can download the tarball of cxxbridge-flags v1.0.134 or view the source online.
no grep hits for cipher, crypto, fs, net, or unsafe