1.1.2 (current) Thoroughness: High Understanding: High
by matthiasbeyer on 2022-09-22
This review is from Crev, a distributed system for code reviews. To add your review, set up cargo-crev.
These reviews are from cargo-vet. To add your review, set up cargo-vet and submit your URL to its registry.
1.1.2 (current)
From google/supply-chain copy of chromium. Audited without comment by Gwendal Grignou.
1.1.2 (current)
From kornelski/crev-proofs copy of salsa.debian.org.
Only in debcargo (unstable). Changelog:
- Package exitcode 1.1.2 from crates.io using debcargo 2.6.0
1.1.2 (current)
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-run
-
This crate can be compiled, run, and tested on a local workstation or in controlled automation without surprising consequences. More…
- crypto-safe
-
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. - unknown
-
May have been packaged automatically without a review
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 exitcode. Alternatively, you can download the tarball of exitcode v1.1.2 or view the source online.
Crate is just a collection of constants with some conveniance functionality added. Should be perfectly fine to use, although the crate seems to be no longer maintained.