0.1.2 (current)
From divviup/libprio-rs. Audited without comment by Brandon Pitman.
These reviews are from cargo-vet. To add your review, set up cargo-vet and submit your URL to its registry.
0.1.2 (current)
From bytecodealliance/wasmtime. By Jamey Sharp.
0.1.2 (current)
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-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 errno-dragonfly is 0.1.2.
0.1.1 (older version) Thoroughness: Medium Understanding: High
Approved without comment by kpcyrd on 2019-08-30
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 errno-dragonfly. Alternatively, you can download the tarball of errno-dragonfly v0.1.2 or view the source online.
This should be portable to any POSIX system and seems like it should be part of the libc crate, but at any rate it's safe as is.