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 cargo

Dependencies

(75 total, 7 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 annotate-snippets^0.12.100.12.13up to date
 anstream^0.6.211.0.0out of date
 anstyle^1.0.131.0.14up to date
 anyhow^1.0.1001.0.102up to date
 base64^0.22.10.22.1up to date
 blake3^1.8.21.8.3up to date
 cargo-credential^0.4.20.4.9up to date
 cargo-credential-libsecret^0.5.50.5.5up to date
 cargo-credential-macos-keychain^0.4.200.4.20up to date
 cargo-credential-wincred^0.4.200.4.20up to date
 cargo-platform^0.3.00.3.2up to date
 cargo-util^0.2.270.2.27up to date
 cargo-util-schemas^0.12.00.12.0up to date
 clap^4.5.534.6.0up to date
 clap_complete^4.5.644.6.0up to date
 color-print^0.3.70.3.7up to date
 crates-io^0.40.170.40.17up to date
 curl^0.4.490.4.49up to date
 curl-sys^0.4.840.4.85+curl-8.18.0up to date
 filetime^0.2.260.2.27up to date
 flate2^1.1.51.1.9up to date
 git2^0.20.30.20.4up to date
 git2-curl^0.21.00.21.0up to date
 gix^0.77.00.80.0out of date
 glob^0.3.30.3.3up to date
 hex^0.4.30.4.3up to date
 hmac^0.12.10.12.1up to date
 home^0.5.120.5.12up to date
 http-auth^0.1.100.1.10up to date
 ignore^0.4.250.4.25up to date
 im-rc^15.1.015.1.0up to date
 indexmap^2.12.12.13.0up to date
 itertools^0.14.00.14.0up to date
 jiff^0.2.170.2.23up to date
 jobserver^0.1.340.1.34up to date
 libc^0.2.1780.2.183up to date
 libgit2-sys^0.18.30.18.3+1.9.2up to date
 memchr^2.7.62.8.0up to date
 opener^0.8.30.8.4up to date
 openssl^0.10.750.10.76up to date
 os_info^3.14.03.14.0up to date
 pasetors^0.7.70.7.8up to date
 pathdiff^0.2.30.2.3up to date
 rand^0.9.20.10.0out of date
 regex^1.12.21.12.3up to date
 rusqlite^0.38.00.39.0out of date
 rustc-hash^2.1.12.1.1up to date
 rustc-stable-hash^0.1.20.1.2up to date
 rustfix^0.9.20.9.4up to date
 same-file^1.0.61.0.6up to date
 semver^1.0.271.0.27up to date
 serde^1.0.2281.0.228up to date
 serde-untagged^0.1.90.1.9up to date
 serde_ignored^0.1.140.1.14up to date
 serde_json^1.0.1481.0.149up to date
 sha1^0.10.60.10.6up to date
 shell-escape^0.1.50.1.5up to date
 supports-hyperlinks^3.2.03.2.0up to date
 supports-unicode^3.0.03.0.0up to date
 tar^0.4.440.4.44up to date
 tempfile^3.24.03.27.0up to date
 thiserror^2.0.172.0.18up to date
 time ⚠️^0.3.440.3.47maybe insecure
 toml^0.9.101.0.7+spec-1.1.0out of date
 toml_edit^0.24.00.25.5+spec-1.1.0out of date
 tracing^0.1.440.1.44up to date
 tracing-chrome^0.7.20.7.2up to date
 tracing-subscriber^0.3.220.3.23up to date
 unicase^2.8.12.9.0up to date
 unicode-ident^1.0.221.0.24up to date
 unicode-width^0.2.20.2.2up to date
 url^2.5.72.5.8up to date
 walkdir^2.5.02.5.0up to date
 windows-sys^0.610.61.2up to date
 winnow^0.7.141.0.0out of date

Dev dependencies

(7 total, 3 outdated)

CrateRequiredLatestStatus
 annotate-snippets^0.12.100.12.13up to date
 cargo-test-support^0.10.00.10.0up to date
 gix^0.77.00.80.0out of date
 gix-transport^0.52.10.55.0out of date
 memfd^0.6.50.6.5up to date
 same-file^1.0.61.0.6up to date
 snapbox^0.6.231.1.0out of date

Security Vulnerabilities

time: Denial of Service via Stack Exhaustion

RUSTSEC-2026-0009

Impact

When user-provided input is provided to any type that parses with the RFC 2822 format, a denial of service attack via stack exhaustion is possible. The attack relies on formally deprecated and rarely-used features that are part of the RFC 2822 format used in a malicious manner. Ordinary, non-malicious input will never encounter this scenario.

Patches

A limit to the depth of recursion was added in v0.3.47. From this version, an error will be returned rather than exhausting the stack.

Workarounds

Limiting the length of user input is the simplest way to avoid stack exhaustion, as the amount of the stack consumed would be at most a factor of the length of the input.