Lib.rs

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

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

by crjeder on 2021-08-04

Only type definition. Nothing dangerous here.

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

by MaulingMonkey on 2019-08-30

Trivial uninhabited type. LGTM.

No unsafe, no I/O, single lib.rs source file, decent docs.

1.0.2 (current) Rating: Strong Positive Thoroughness: Medium Understanding: Medium

Approved without comment by git.sr.ht/~icefox on 2019-08-20

1.0.2 (current) Rating: Strong Positive Thoroughness: Medium Understanding: High

Approved without comment by dpc on 2019-01-12

---

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

1.0.2 (current) safe-to-deploy

From mozilla/supply-chain copy of hg. By Bobby Holley.

Very small crate, just hosts the Void type for easier cross-crate interfacing.

1.0.2 (current) does-not-implement-crypto, safe-to-deploy

From google/supply-chain copy of chromium. Audited without comment by George Burgess IV.

1.0.2 (current) safe-to-run

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

Packaged for Debian (stable). Changelog:

• Package void 1.0.2 from crates.io using debcargo 2.1.1

1.0.2 (current) unknown

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

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

No unsafe code.

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

ub-risk-1 (implies ub-risk-2)

Implied by other criteria

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

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

Implied by other criteria

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

unknown

May have been packaged automatically without a review