0.4.13 (current)
From google/supply-chain copy of google/rust-crate-audits. By Luca Versari.
These reviews are from cargo-vet. To add your review, set up cargo-vet
and submit your URL to its registry.
0.4.13 (current)
From google/supply-chain copy of google/rust-crate-audits. By Luca Versari.
0.4.13 (current)
From kornelski/crev-proofs copy of salsa.debian.org.
Only in debcargo (unstable). Changelog:
The current version of IsTerminal is 0.4.13.
0.4.12 — diff review from 0.4.9 only (older version)
From zcash/rust-ecosystem copy of zcash/librustzcash. Audited without comment by Daira Emma Hopwood.
0.4.10 (older version)
From kornelski/crev-proofs copy of git.savannah.gnu.org.
Packaged for Guix (crates-io)
0.4.9 — diff review from 0.4.2 only (older version)
From google/supply-chain copy of chromium. Audited without comment by George Burgess IV.
0.4.7 (older version)
From bytecodealliance/wasmtime. By Dan Gohman.
The is-terminal implementation code is now sync'd up with the prototype implementation in the Rust standard library.
0.4.3 — diff review from 0.4.1 only (older version)
From bytecodealliance/wasmtime. By Pat Hickey.
The Bytecode Alliance is the author of this crate.
0.3.0 (older version)
From bytecodealliance/wasmtime. By Alex Crichton.
Contains only unsafe code for interacting with the crate's intended purpose.
cargo-vet does not verify reviewers' identity. You have to fully trust the source the audits are from.
This crate can be compiled, run, and tested on a local workstation or in controlled automation without surprising consequences. More…
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.
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.
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
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
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
This crate will not introduce a serious security vulnerability to production software exposed to untrusted input. More…
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 IsTerminal is 0.4.13.
0.4.12 (older version) Thoroughness: Low Understanding: Medium
by weiznich on 2024-02-29
Review update from 0.4.9 to 0.4.12
0.3.0 (older version) Thoroughness: High Understanding: High
by git.jcg.re/jcgruenhage/crev-proofs.git on 2022-09-19
Following up my review of atty, this is the alternative that I'm recommending. The crate is well-maintained and has the soundness problem from atty fixed. The dependencies have been changed around a bit, with rustix replacing libc, and windows-sys replacing win-api. This means that there's a bit less unsafe code in the library here as well.
The API surface changed a bit as well, but I'd claim that the new API is more sensible and allows usage on any file descriptor instead of just stdin/stdout/stderr.
Finally, this has one additional dependency, io-lifetimes
, by the same
author. I have not reviewed the implementation, but it's been merged into Rust
itself and stabilized with 1.63, so I am not worrying about it too much.
Lib.rs has been able to verify that all files in the crate's tarball, except Cargo.lock
,
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 is-terminal
. Alternatively, you can download the tarball of is-terminal v0.4.13 or view the source online.
Reviewed in CL 666758546