Code reviews of the openssl-probe crate // Lib.rs

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

0.1.5 (current) Rating: Positive Thoroughness: High Understanding: High

Approved without comment by kpcyrd on 2023-12-31

The current version of openssl-probe is 0.1.5.

0.1.2 (older version) Rating: Positive Thoroughness: High Understanding: High

by mibmo on 2021-01-26

A crate for finding system CA locations

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

Approved without comment by kornelski on 2019-07-22

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

0.1.5 (current) safe-to-deploy

From bytecodealliance/wasmtime. By Pat Hickey.

IO is only checking for the existence of paths in the filesystem

The current version of openssl-probe is 0.1.5.

0.1.2 (older version) safe-to-run

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

Packaged for Debian (stable). Changelog:

Package openssl-probe 0.1.2 from crates.io using debcargo 2.2.1

0.1.2 (older version) unknown

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.

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

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

safe-to-run

This crate can be compiled, run, and tested on a local workstation or in controlled automation without surprising consequences. More…

unknown

May have been packaged automatically without a review

Lib.rs has been able to verify that all files in the crate's tarball, except Cargo.lock, 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 openssl-probe. Alternatively, you can download the tarball of openssl-probe v0.1.5 or view the source online.