Lib.rs

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

2.4.1 (current) unknown

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

Only in debcargo (unstable). Changelog:

• Team upload.
• Package half 2.4.1 from crates.io using debcargo 2.6.1

The current version of half is 2.4.1.

2.4.0 (older version) ub-risk-1

From google/supply-chain copy of google/rust-crate-audits. By Benjamin Saunders.

Reviewed in CL 610738461

2.3.1 (older version) unknown

From kornelski/crev-proofs copy of git.savannah.gnu.org.

Packaged for Guix (crates-io)

2.2.1 — diff review from 1.8.2 only (older version) safe-to-run

From zcash/rust-ecosystem copy of zcash/librustzcash. By Daira Emma Hopwood.

All new uses of unsafe are either just accessing bit representations, or plausibly reasonable uses of intrinsics. I have not checked safety requirements on the latter.

1.8.2 (older version) safe-to-deploy

From mozilla/supply-chain copy of hg. By John Schanck.

This crate contains unsafe code for bitwise casts to/from binary16 floating-point format. I've reviewed these and found no issues. There are no uses of ambient capabilities.

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

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

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-1 (implies ub-risk-2)

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

ub-risk-2 (implies ub-risk-3)

Implied by other criteria

Negligible unsoundness or average 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-2

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

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

---

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

The current version of half is 2.4.1.

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

by weiznich on 2024-02-29

Review update from 1.8.2 to 2.4.0

• Added dependency on cfg-if
• Added optional dependencies on rand, rkyv
• Inline/must_use annotation
• More functions to match stdlib

1.8.2 (older version) Rating: Positive Thoroughness: Medium Understanding: Medium

by ThomasdenH on 2022-01-11

A small crate to find the rust compiler version as well as some metadata. Contains plenty of tests and handles versioning quirks

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

Approved without comment by dpc on 2019-01-11