Lib.rs

› atty › Reviews
RUSTSEC-2024-0375 (unmaintained) on 2024-09-25: atty is unmaintained

The maintainer of atty has published an official notice that the crate is no longer under development, and that users should instead rely on the functionality in the standard library's IsTerminal trait.

Alternative(s)

  • std::io::IsTerminal - Stable since Rust 1.70.0 and the recommended replacement per the atty maintainer.
  • is-terminal - Standalone crate supporting Rust older than 1.70.0
RUSTSEC-2021-0145 (unsound) on 2021-07-04: Potential unaligned read

On windows, atty dereferences a potentially unaligned pointer.

In practice however, the pointer won't be unaligned unless a custom global allocator is used.

In particular, the System allocator on windows uses HeapAlloc, which guarantees a large enough alignment.

atty is Unmaintained

A Pull Request with a fix has been provided over a year ago but the maintainer seems to be unreachable.

Last release of atty was almost 3 years ago.

Possible Alternative(s)

The below list has not been vetted in any way and may or may not contain alternatives;

https://github.com/softprops/atty/pull/51

https://github.com/softprops/atty/issues/57

GHSA-g98v-hv3f-hcfr

These reviews are from Crev, a distributed system for code reviews. To add your review, set up cargo-crev.

0.2.14 (current) Rating: Positive Thoroughness: Medium Understanding: Medium

by matthiasbeyer on 2022-09-22

Simple codebase, looks good. Did not look at the cfg(windows) code.

0.2.14 (current) Rating: Positive Thoroughness: Medium Understanding: Medium

by vlad20012 on 2021-09-15

This version only adds support for target_os = "hermit" via hermit_abi crate. The rest of the code in the crate has not been changed.

0.2.14 (current) Rating: Positive Thoroughness: Low Understanding: Medium

by andrewaylett on 2021-04-08

Code changes are minimal and sensible.

The current version of atty is 0.2.14.

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

Approved without comment by kornelski on 2019-08-22

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

by git.sr.ht/~icefox on 2019-08-22

Small platform-functionality wrapper, nothing exciting.

These reviews are from cargo-vet. To add your review, set up cargo-vet and submit your URL to its registry.

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.

unknown

May have been packaged automatically without a review

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 atty. Alternatively, you can download the tarball of atty v0.2.14 or view the source online.