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 SyncWrapper is 1.0.1.

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


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.

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.


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 SyncWrapper is 1.0.1.

0.1.1 (older version) Rating: Strong Positive Thoroughness: Medium Understanding: High

by niklasf on 2021-10-16

Reviewed for soundness. There are two instances of unsafe code.

One is a standard pin projection.

The other is the primary purpose of the crate:

unsafe impl Sync for SyncWrapper {}

This is equivalent to the statement that all instances of &SyncWrapper can be safely sent across thread boundaries. This is true, because &SyncWrapper is useless. The crate allows no operations on &SyncWrapper alltogether. The only provided methods require &mut SyncWrapper or owned SyncWrapper.

Crates in the 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 sync_wrapper. Alternatively, you can download the tarball of sync_wrapper v1.0.1 or view the source online.