Lib.rs

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

0.4.3 (current) ub-risk-0, does-not-implement-crypto

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

Reviewed in CL 581228675

0.4.3 (current) unknown

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

Packaged for Guix (crates-io)

0.4.3 (current) unknown

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

Only in debcargo (unstable). Changelog:

• Package btoi 0.4.3 from crates.io using debcargo 2.6.0

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

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

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.

unknown

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 btoi is 0.4.3.

0.4.2 (older version) Rating: Positive Thoroughness: High Understanding: High

by niklasf on 2020-02-18

Parses integers directly from ASCII byte slices.

As the author of this crate, I tried to apply relevant best practices. I have high confidence in its correctness.

• Rust API guidelines checklist complete, except C-STABLE, due to the num-traits dependency.
• No unsafe code.
• Using quickcheck for fuzz testing (no panics, equivalent to str::from_utf8() followed by {integer}::from_str_radix() from the standard library).