1.0.9 (current)
From google/supply-chain copy of chromium. By George Burgess IV.
These reviews are from cargo-vet. To add your review, set up cargo-vet
and submit your URL to its registry.
1.0.9 (current)
From google/supply-chain copy of chromium. By George Burgess IV.
1.0.9 (current)
From kornelski/crev-proofs copy of salsa.debian.org.
Only in debcargo (unstable). Changelog:
1.0.9 (current)
From kornelski/crev-proofs copy of git.savannah.gnu.org.
Packaged for Guix (crates-io)
The current version of link-cplusplus is 1.0.9.
1.0.8 — diff review from 1.0.7 only (older version)
From zcash/rust-ecosystem copy of zcash/zcash. Audited without comment by Jack Grigg.
1.0.5 (older version)
From google/supply-chain copy of chromium. Audited without comment by ChromeOS.
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
These reviews are from Crev, a distributed system for code reviews. To add your review, set up cargo-crev
.
The current version of link-cplusplus is 1.0.9.
1.0.6 (older version) Thoroughness: High Understanding: High
by Minoru on 2022-03-23
This update removes an implicit dependency on std and declares MSRV of 1.34. No changes to the actual code, so my review for 1.0.4 stands.
1.0.5 (older version) Thoroughness: High Understanding: High
by Minoru on 2021-03-24
The delta since 1.0.4 only shows documentation changes. They also added Clippy to the CI, which is nice.
No changes to the code, so my 1.0.4 review stands.
Lib.rs has been able to verify that all files in the crate's tarball 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 link-cplusplus
. Alternatively, you can download the tarball of link-cplusplus v1.0.9 or view the source online.
This crate exists simply to link with libcxx or libstdcxx. No assertions are made about the safety of either of those libraries. :)