0.2.19 (current)
From google/supply-chain copy of chromium. By Manish Goregaokar.
These reviews are from cargo-vet. To add your review, set up cargo-vet and submit your URL to its registry.
0.2.19 — diff review from 0.2.18 only (current)
From divviup/libprio-rs. Audited without comment by David Cook.
0.2.19 (current)
From bytecodealliance/wasmtime. By Andrew Brown.
As advertised: a numeric library. The only unsafe is from some float-to-int conversions, which seems expected.
0.2.19 (current)
From kornelski/crev-proofs copy of git.savannah.gnu.org.
Packaged for Guix (crates-io)
0.2.19 (current)
From kornelski/crev-proofs copy of salsa.debian.org.
Only in debcargo (unstable). Changelog:
- Team upload.
- Expand dont-run-mipsel-failing-doctests.diff to cover a new max() case, fixing FTBFS on mips64el.
The current version of num-traits is 0.2.19.
0.2.17 — diff review from 0.2.16 only (older version)
From divviup/libprio-rs. Audited without comment by Ameer Ghani.
0.2.16 — diff review from 0.2.15 only (older version)
From google/supply-chain copy of chromium. Audited without comment by George Burgess IV.
0.2.15 (older version)
From mozilla/supply-chain copy of hg. By Josh Stone.
All code written or reviewed by Josh Stone.
0.2.14 (older version)
From google/supply-chain copy of chromium. Audited without comment by Android Legacy.
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 impliescrypto-safe, but does not require expert review in order to audit for.- safe-to-deploy (implies safe-to-run)
-
This crate will not introduce a serious security vulnerability to production software exposed to untrusted input. More…
- 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
- 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
These reviews are from Crev, a distributed system for code reviews. To add your review, set up cargo-crev.
The current version of num-traits is 0.2.19.
0.2.14 (older version) Thoroughness: Medium Understanding: Medium
by kaiserkarel on 2022-01-17
No backdoors etc found, mainly looked at risks for supply-chain attacks.
0.2.14 (older version) Thoroughness: None Understanding: Low
by inflation on 2021-11-08
Used by almost everyone
0.2.11 (older version) Thoroughness: Medium Understanding: High
by HeroicKatora on 2020-04-29
With a prior parsing bug fixed and Rust soon stabilizing floating point to integer conversion without UB the previous reservations no longer hold. It looks stable as is and doesn't attempt anything far fetched.
0.2.11 (older version) Thoroughness: None Understanding: High
by niklasf on 2020-01-18
num-traits provides traits for writing code generic over numeric types and implementations for built-in numeric types. I exclusively reviewed unsafe code.
num-traits uses some instances of unsafe code. Each unsafe block has a comment explaining why it is required and why it is sound. The blocks are easy to understand and check locally.
0.2.8 (older version) Thoroughness: Medium Understanding: Medium
by git.sr.ht/~icefox on 2019-08-23
Mostly just traits; unsafe can probably be removed, see https://github.com/rust-num/num-traits/issues/123
0.2.6 (older version) Thoroughness: Low Understanding: Low
Approved without comment by Canop on 2019-07-05
0.1.43 (older version) Thoroughness: Medium Understanding: Medium
by git.sr.ht/~icefox on 2019-08-23
Show review…
Nothing but a re-export of num-traits 0.2
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 num-traits. Alternatively, you can download the tarball of num-traits v0.2.19 or view the source online.
Contains a single line of float-to-int unsafe with decent safety comments