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 native-tls is 0.2.14.

0.2.11 (older version) safe-to-deploy

From bytecodealliance/wasmtime. By Pat Hickey.

build is only looking for environment variables to set cfg. only two minor uses of unsafe,on macos, with ffi bindings to digest primitives and libc atexit. otherwise, this is an abstraction over three very complex systems (schannel, security-framework, and openssl) which may end up having subtle differences, but none of those are apparent from the implementation of this crate

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
Implied by other criteria

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


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

The current version of native-tls is 0.2.14.

0.2.3 (older version) Rating: Positive Thoroughness: Low Understanding: Low

Approved without comment by kornelski on 2019-07-08


Crates in the crates.io registry are tarball snapshots uploaded by crates' publishers. The registry is not using crates' git repositories. There is absolutely no guarantee that the repository URL declared by the crate belongs to the crate, or that the code in the repository is the code inside the published tarball.

To review the actual code of the crate, it's best to use cargo crev open native-tls. Alternatively, you can download the tarball of native-tls v0.2.14 or view the source online.