Lib.rs

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 CC is 1.0.96.

1.0.94 — diff review from 1.0.83 only (older version) safe-to-deploy

From zcash/rust-ecosystem copy of zcash/zcash. By Daira Emma Hopwood.

The optimization to use buffer.set_len(buffer.capacity()) in command_helpers::StderrForwarder::forward_available doesn't look panic-safe: if stderr.read panics and that panic is caught by a caller of forward_available, then the inner buffer of StderrForwarder will contain uninitialized data. This looks difficult to trigger in practice, but I have opened an issue https://github.com/rust-lang/cc-rs/issues/1036.

parallel::async_executor contains unsafe pinning code but it looks reasonable. Similarly for the unsafe initialization code in parallel::job_token::JobTokenServer and file operations in parallel::stderr.

This crate executes commands, and my review is likely not sufficient to detect subtle backdoors. I did not review the use of library handles in the com package on Windows.

1.0.83 — diff review from 1.0.82 only (older version) safe-to-run, does-not-implement-crypto

From google/supply-chain copy of chromium. Audited without comment by George Burgess IV.

1.0.83 — diff review from 1.0.78 only (older version) safe-to-deploy

From mozilla/supply-chain copy of mozilla/glean. Audited without comment by Jan-Erik Rediger.

1.0.83 (older version) unknown

From kornelski/crev-proofs copy of git.savannah.gnu.org.

Packaged for Guix (crates-io)

1.0.83 (older version) unknown

From kornelski/crev-proofs copy of salsa.debian.org.

Only in debcargo (unstable). Changelog:

• Team upload.
• Package cc 1.0.83 from crates.io using debcargo 2.6.0

1.0.78 — diff review from 1.0.73 only (older version) safe-to-deploy

From mozilla/supply-chain copy of hg. Audited without comment by Mike Hommey.

1.0.73 (older version) safe-to-deploy

From bytecodealliance/wasmtime. By Alex Crichton.

I am the author of this crate.

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 implies crypto-safe, but does not require expert review in order to audit for.

safe-to-deploy (implies safe-to-run)

This crate will not introduce a serious security vulnerability to production software exposed to untrusted input. More…

unknown

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 CC is 1.0.96.

1.0.59 (older version) Rating: Neutral Thoroughness: None Understanding: Low

by inflation on 2021-11-08

Used by almost everyone

1.0.28 (older version) Rating: Positive Thoroughness: Low Understanding: Medium

Approved without comment by kornelski on 2019-01-06