0.2.8 — diff review from 0.2.7 only (current)
From zcash/rust-ecosystem copy of zcash/zcash. By str4d.
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 libm is 0.2.8.
0.2.7 — diff review from 0.2.4 only (older version)
From bytecodealliance/wasmtime. By Alex Crichton.
This is a minor update which has some testing affordances as well as some updated math algorithms.
0.2.7 (older version)
From kornelski/crev-proofs copy of salsa.debian.org.
Only in debcargo (unstable). Changelog:
- Team upload.
- Package libm 0.2.7 from crates.io using debcargo 2.6.0
- Update features.patch for new upstream.
- Add patch (submitted as pull-request upstream) to fix rint and rintf on x87.
- Drop other patches, they are either merged upstream or rendered obsolete by upstream changes.
0.2.6 (older version)
From mozilla/supply-chain copy of hg. By Makoto Kato.
This crate uses unsafe block, but this doesn't have network and file access. I audited code.
0.2.6 — diff review from 0.2.5 only (older version)
From zcash/rust-ecosystem copy of zcash/zcash. Audited without comment by Jack Grigg.
0.2.6 (older version)
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
Implied by other criteria
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
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 libm. Alternatively, you can download the tarball of libm v0.2.8 or view the source online.
Forces some intermediate values to not have too much precision on the x87 FPU.