Code reviews of the PKG_CONFIG crate // Lib.rs

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

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

From google/supply-chain copy of chromium. Audited without comment by Justin Green.

The current version of PKG_CONFIG is 0.3.31.

0.3.30 — diff review from 0.3.29 only (older version) safe-to-deploy

From zcash/rust-ecosystem copy of zcash/librustzcash. Audited without comment by Daira Emma Hopwood.

0.3.29 — diff review from 0.3.26 only (older version) safe-to-deploy

From bytecodealliance/wasmtime. By Alex Crichton.

No unsafe additions or anything outside of the purview of the crate in this change.

0.3.27 (older version) unknown

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

Only in debcargo (unstable). Changelog:

Package pkg-config 0.3.27 from crates.io using debcargo 2.6.1

[ Blair Noctis ]

Team upload.
Package pkg-config 0.3.26 from crates.io using debcargo 2.6.0 (Closes: #1056179)

0.3.27 (older version) unknown

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

Packaged for Guix (crates-io)

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

From google/supply-chain copy of chromium. Audited without comment by Alexandre Courbot.

0.3.26 — diff review from 0.3.25 only (older version) safe-to-deploy

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

0.3.25 (older version) safe-to-deploy

From bytecodealliance/wasmtime. By Pat Hickey.

This crate shells out to the pkg-config executable, but it appears to sanitize inputs reasonably.

cargo-vet does not verify reviewers' identity. You have to fully trust the source the audits are from.

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-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…

unknown

May have been packaged automatically without a review

This review is from Crev, a distributed system for code reviews. To add your review, set up cargo-crev.

The current version of PKG_CONFIG is 0.3.31.

0.3.19 (older version) Rating: Positive Thoroughness: Medium Understanding: Medium

Approved without comment by kornelski on 2021-02-02

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