Lib.rs

› memoffset › Reviews

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 memoffset is 0.9.1.

0.9.0 — diff review from 0.8.0 only (older version) safe-to-deploy

From zcash/rust-ecosystem copy of zcash/zcash. By str4d.

Refactors the offset_of macros to optionally replace their existing unsafe implementations with the unstable internal core::mem::offset_of macro. The existing unsafe implementations are unaltered.

0.6.5 (older version) safe-to-run

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

Packaged for Debian (stable). Changelog:

  • Team upload.
  • Package memoffset 0.6.5 from crates.io using debcargo 2.5.0
    • fixes building the "unstable_const" feature with rustc 1.59

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.

ub-risk-3 (implies ub-risk-4)

Mild unsoundness or suboptimal soundness.

Full description of the audit criteria can be found at https://github.com/google/rust-crate-audits/blob/main/auditing_standards.md#ub-risk-3

ub-risk-4
Implied by other criteria

Extreme unsoundness.

Full description of the audit criteria can be found at https://github.com/google/rust-crate-audits/blob/main/auditing_standards.md#ub-risk-4

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

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

The current version of memoffset is 0.9.1.

0.6.5 (older version) Rating: Positive Thoroughness: Low Understanding: Medium

Approved without comment by dpc on 2022-01-17

0.5.5 (older version) Rating: Neutral Thoroughness: Low Understanding: Low

by kornelski on 2020-09-15

0.5.3 (older version) Rating: Neutral Thoroughness: Low Understanding: Medium

by leo60228 on 2020-01-06

Simple crate. Triggers UB but there is no workaround on current Rust.

  • Issue: Low (24)

0.5.1 (older version) Rating: Negative Thoroughness: Low Understanding: Medium

by dpc on 2019-08-25

Show review…

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