- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
The maintainer has advised that this crate is deprecated and will not receive any maintenance.
The crate does not seem to have much dependencies and may or may not be ok to use as-is.
Last release seems to have been three years ago.
## Possible Alternative(s)
The below list has not been vetted in any way and may or may not contain alternatives;
- [ansiterm](https://crates.io/crates/ansiterm) - [anstyle](https://github.com/epage/anstyle) - [console](https://crates.io/crates/console) - [nu-ansi-term](https://crates.io/crates/nu-ansi-term) - [owo-colors](https://crates.io/crates/owo-colors) - [stylish](https://crates.io/crates/stylish) - [yansi](https://crates.io/crates/yansi)
## Dependency Specific Migration(s)
- [structopt, clap2](https://github.com/clap-rs/clap/discussions/4172)
Is RUSTSEC-2021-0139 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | ansi_term | >=0.0.0-0 |
no fix listed |
References
Sources
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.