Lib.rs

› libc › Reviews

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 libc is 0.2.169.

0.2.159 (older version) unknown

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

Only in debcargo (unstable). Changelog:

  • Team upload.
  • Package libc 0.2.159 from crates.io using debcargo 2.7.1
  • Update time64-04-use-time64-symbols.patch with moved ioctl, ctime_r

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

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

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 libc is 0.2.169.

0.2.155 (older version) Rating: Positive Thoroughness: None Understanding: Medium

by bash on 2024-08-19

Official rust-lang package

0.2.139 (older version) Rating: Positive Thoroughness: Low Understanding: Medium

by Minoru on 2022-12-24

Compared to 0.2.138, the bulk of the changes are support for new target_os, nto, which is QNX/Neutrino. I glanced through them, they seem to have the right shape. The rest of the changes are the usual: new constants and new function declarations. The only interesting bit there is a new KERNEL_VERSION function which emulates the eponymous macro; it returns the kernel version, limiting the patch version to 255 (for compatibility).

As usual, "thoroughness" for this review is "low" because I didn't manually check that the bindings match the headers — I trust that the CI checked that already.

0.2.138 (older version) Rating: Positive Thoroughness: Low Understanding: Medium

by Minoru on 2022-12-24

Show review…

Compared to 0.2.137, this version adds some new constants and bindings. The only interesting bit is two new wrappers in unix::solarish::compat module that wrap getpwent_r and getgrent_r functions in such a way that calls don't modify errno. The wrappers look solid to me.

As usual, "thoroughness" for this review is "low" because I didn't manually check that the bindings match the headers — I trust that the CI checked that already.

0.2.86 (older version) Rating: Positive Thoroughness: Low Understanding: Medium

by inflation on 2021-11-08

Used by almost everyone

0.2.62 (older version) Rating: Neutral Thoroughness: Low Understanding: Medium

by Lokathor on 2019-09-04

Crates in the crates.io registry are tarball snapshots uploaded by crates' publishers. The registry is not using crates' git repositories. There is absolutely no guarantee that the repository URL declared by the crate belongs to the crate, or that the code in the repository is the code inside the published tarball.

To review the actual code of the crate, it's best to use cargo crev open libc. Alternatively, you can download the tarball of libc v0.2.169 or view the source online.