Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RUSTSEC-2024-0375: atty is unmaintained #456

Open
github-actions bot opened this issue Sep 27, 2024 · 1 comment · May be fixed by #457
Open

RUSTSEC-2024-0375: atty is unmaintained #456

github-actions bot opened this issue Sep 27, 2024 · 1 comment · May be fixed by #457

Comments

@github-actions
Copy link
Contributor

atty is unmaintained

Details
Status unmaintained
Package atty
Version 0.2.14
URL softprops/atty#57
Date 2024-09-25

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

See advisory page for additional details.

@matheus23
Copy link
Member

This is a development dependency in wnfs-bench:

$ cargo tree -i atty
warning: virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
note: to keep the current resolver, specify `workspace.resolver = "1"` in the workspace root's manifest
note: to use the edition 2021 resolver, specify `workspace.resolver = "2"` in the workspace root's manifest
note: for more details see https://doc.rust-lang.org/cargo/reference/resolver.html#resolver-versions
atty v0.2.14
└── criterion v0.4.0
    [dev-dependencies]
    └── wnfs-bench v0.2.0 (/home/philipp/program/work/rs-wnfs/wnfs-bench)

The fix is to update criterion.

@matheus23 matheus23 linked a pull request Sep 27, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant