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

0.1.0 (current) Rating: Positive Thoroughness: Low Understanding: Low

Approved without comment by kornelski on 2021-05-17

0.1.0 (current) Rating: Positive Thoroughness: Medium Understanding: Medium

by mibmo on 2021-01-26

Simple types for unsafe pinning

The current version of pin-utils is 0.1.0.

0.1.0-alpha.4 (older version) Rating: Strong Positive Thoroughness: Low Understanding: Medium

by leo60228 on 2020-01-06

Very small crate, has useful macros

0.1.0-alpha.4 (older version) Rating: Positive Thoroughness: Medium Understanding: Medium

by bitwave on 2019-11-13

simple macros to work with the Pin and Unpin types


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

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…

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


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