Lib.rs

› Errno › 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 Errno is 0.3.9.

0.3.8 (older version) unknown

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

Only in debcargo (unstable). Changelog:

  • Package errno 0.3.8 from crates.io using debcargo 2.6.1
  • Drop no-dragonfly.patch, no longer needed.
  • Update no-windows.patch for new upstream.

[ Blair Noctis ]

  • Team upload.
  • Package errno 0.3.3 from crates.io using debcargo 2.6.0
  • Set collapse_features = true

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
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 Errno is 0.3.9.

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

by weiznich on 2024-02-29

Review update from 0.3.5 to 0.3.8

  • Bump windows-sys depnendency
  • Tweak target support

0.2.5 (older version) Rating: Positive Thoroughness: Medium Understanding: Medium

by Minoru on 2020-05-08

I evaluated this before using in my own project. I only really know Linux, but WASI and Windows parts made sense to me as well. I can't vouch for memory safety of WinAPI calls, so I capped the rating at "positive" rather than giving it the "strong" that it probably deserves.

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

by pickfire on 2020-05-07

read into how errno work and why is it not in libc

Lib.rs has been able to verify that all files in the crate's tarball are in the crate's repository. 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 errno. Alternatively, you can download the tarball of errno v0.3.9 or view the source online.