This project might be open to known security vulnerabilities, which can be prevented by tightening the version range of affected dependencies. Find detailed information at the bottom.

Crate clippy-wrapper

No external dependencies! 🙌

Crate micromux

Dependencies

(11 total, all up-to-date)

CrateRequiredLatestStatus
 shlex^2.0.12.0.1up to date
 nix^0.31.30.31.3up to date
 filedescriptor^0.8.30.8.3up to date
 alacritty_terminal^0.26.00.26.0up to date
 portable-pty^0.90.9.0up to date
 petgraph^00.8.3up to date
 directories^66.0.0up to date
 humantime^22.4.0up to date
 shellexpand^33.1.2up to date
 unindent^00.2.4up to date
 yaml-spanned^00.0.3up to date

Dev dependencies

(3 total, 1 possibly insecure)

CrateRequiredLatestStatus
 jsonschema^00.48.2up to date
 serde_json^11.0.151up to date
 serde_yaml ⚠️^00.9.34+deprecatedmaybe insecure

Crate micromux-tui

Dependencies

(5 total, all up-to-date)

CrateRequiredLatestStatus
 ratatui=0.30.20.30.2up to date
 ansi-to-tui^88.0.1up to date
 strip-ansi-escapes^00.2.1up to date
 crossterm^0.290.29.0up to date
 tokio-stream^00.1.18up to date

Crate micromux-cli

Dependencies

(4 total, 1 possibly insecure)

CrateRequiredLatestStatus
 tracing-subscriber ⚠️^00.3.23maybe insecure
 tracing-appender^00.2.5up to date
 termcolor^11.4.1up to date
 clap^44.6.3up to date

Crate micromux-screenshot

Dependencies

(2 total, all up-to-date)

CrateRequiredLatestStatus
 portable-pty^0.90.9.0up to date
 vt100^00.16.2up to date

Security Vulnerabilities

serde_yaml: Uncontrolled recursion leads to abort in deserialization

RUSTSEC-2018-0005

Affected versions of this crate did not properly check for recursion while deserializing aliases.

This allows an attacker to make a YAML file with an alias referring to itself causing an abort.

The flaw was corrected by checking the recursion depth.

tracing-subscriber: Logging user input may result in poisoning logs with ANSI escape sequences

RUSTSEC-2025-0055

Previous versions of tracing-subscriber were vulnerable to ANSI escape sequence injection attacks. Untrusted user input containing ANSI escape sequences could be injected into terminal output when logged, potentially allowing attackers to:

  • Manipulate terminal title bars
  • Clear screens or modify terminal display
  • Potentially mislead users through terminal manipulation

In isolation, impact is minimal, however security issues have been found in terminal emulators that enabled an attacker to use ANSI escape sequences via logs to exploit vulnerabilities in the terminal emulator.

This was patched in PR #3368 to escape ANSI control characters from user input.