1.0.0 (current) Thoroughness: Low Understanding: Medium
by inflation on 2021-11-08
These reviews are from Crev, a distributed system for code reviews. To add your review, set up cargo-crev
.
1.0.0 (current) Thoroughness: Low Understanding: Medium
by inflation on 2021-11-08
1.0.0 (current) Thoroughness: Low Understanding: Medium
by leo60228 on 2021-09-28
only minor changes
1.0.0 (current) Thoroughness: High Understanding: High
by fkohlgrueber on 2021-09-10
Thorough review of the macro, looks correct. Repo is maintained.
1.0.0 (current) Thoroughness: Low Understanding: Medium
Approved without comment by 3541 on 2020-12-17
The current version of cfg-if is 1.0.0.
0.1.10 (older version) Thoroughness: Medium Understanding: Low
by gitlab.com/chrysn on 2020-04-02
Straightforward macro-only crate.
0.1.10 (older version) Thoroughness: Low Understanding: Low
by MaulingMonkey on 2019-09-25
Macro black magic... I trust the author and what I do understand looks good.
0.1.9 (older version) Thoroughness: Low Understanding: Medium
by git.sr.ht/~icefox on 2019-08-21
Does nothing but shuffle #[cfg] statements; harmless.
These reviews are from cargo-vet. To add your review, set up cargo-vet
and submit your URL to its registry.
1.0.0 (current)
From bytecodealliance/wasmtime. By Alex Crichton.
I am the author of this crate.
1.0.0 (current)
From google/supply-chain copy of chromium. Audited without comment by George Burgess IV.
1.0.0 (current)
From google/supply-chain copy of chromium. Audited without comment by Android Legacy.
1.0.0 (current)
From google/supply-chain copy of chromium. By Lukasz Anforowicz.
I grepped for "unsafe", "crypt", "cipher", "fs", "net" - there were
no hits. This is a really small crate (only lib.rs
which is less than 200
lines + one end-to-end test) so I also skimmed through the macro's definition
and everything looks okay to me.
1.0.0 (current)
From kornelski/crev-proofs copy of salsa.debian.org.
Packaged for Debian (stable). Changelog:
1.0.0 (current)
From kornelski/crev-proofs copy of git.savannah.gnu.org.
Packaged for Guix (crates-io)
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
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 cfg-if
. Alternatively, you can download the tarball of cfg-if v1.0.0 or view the source online.
This crate is used by rustc itself