Code reviews of the rustc_version crate // Lib.rs

These reviews are from cargo-vet. To add your review, set up cargo-vet and submit your URL to its registry.

From mozilla/supply-chain copy of hg. By Nika Layzell.

Straightforward crate which runs $RUSTC -vV and parses the output into a machine-interpretable form for build scripts.

0.4.0 (current) safe-to-deploy

From zcash/rust-ecosystem copy of zcash/zcash. By str4d.

Most of the crate is code to parse and validate the output of rustc -vV. The caller can choose which rustc to use, or can use rustc_version::{version, version_meta} which will try $RUSTC followed by rustc.

If an adversary can arbitrarily set the $RUSTC environment variable then this crate will execute arbitrary code. But when this crate is used within a build script, $RUSTC should be set correctly by cargo.

0.4.0 (current) safe-to-run, does-not-implement-crypto

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.

0.4.0 (current) unknown

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

Packaged for Guix (crates-io)

The current version of rustc_version is 0.4.0.

0.2.3 (older version) safe-to-run, does-not-implement-crypto

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

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…

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

This crate will not introduce a serious security vulnerability to production software exposed to untrusted input. 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.

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 rustc_version is 0.4.0.

0.3.0 (older version) Rating: Positive Thoroughness: Medium Understanding: High

by programmerjake on 2020-11-05

read through v0.3.0 code after contributing to master version

0.2.3 (older version) Rating: Neutral Thoroughness: Medium Understanding: Medium

by git.sr.ht/~icefox on 2019-08-20

It can be told to execute arbitrary programs via env var, but does nothing malicious itself.

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 rustc_version. Alternatively, you can download the tarball of rustc_version v0.4.0 or view the source online.