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

(74 total, 3 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 annotate-snippets^0.11.50.11.5up to date
 anstream^0.6.180.6.18up to date
 anstyle^1.0.101.0.10up to date
 anyhow^1.0.951.0.98up to date
 base64^0.22.10.22.1up to date
 blake3^1.5.51.8.2up to date
 cargo-credential^0.4.20.4.8up to date
 cargo-credential-libsecret^0.4.130.4.13up to date
 cargo-credential-macos-keychain^0.4.130.4.13up to date
 cargo-credential-wincred^0.4.130.4.13up to date
 cargo-platform^0.2.00.2.0up to date
 cargo-util^0.2.200.2.20up to date
 cargo-util-schemas^0.8.10.8.1up to date
 clap^4.5.284.5.39up to date
 clap_complete^4.5.444.5.52up to date
 color-print^0.3.70.3.7up to date
 crates-io^0.40.100.40.10up to date
 curl^0.4.470.4.47up to date
 curl-sys^0.4.790.4.80+curl-8.12.1up to date
 filetime^0.2.250.2.25up to date
 flate2^1.0.351.1.1up to date
 git2^0.20.00.20.2up to date
 git2-curl^0.21.00.21.0up to date
 gix^0.70.00.72.1out of date
 glob^0.3.20.3.2up to date
 hex^0.4.30.4.3up to date
 hmac^0.12.10.12.1up to date
 home^0.5.110.5.11up to date
 http-auth^0.1.100.1.10up to date
 ignore^0.4.230.4.23up to date
 im-rc^15.1.015.1.0up to date
 indexmap^2.7.12.9.0up to date
 itertools^0.14.00.14.0up to date
 jiff^0.2.30.2.14up to date
 jobserver^0.1.320.1.33up to date
 lazycell^1.3.01.3.0up to date
 libc^0.2.1690.2.172up to date
 libgit2-sys^0.18.00.18.1+1.9.0up to date
 memchr^2.7.42.7.4up to date
 opener^0.7.20.8.2out of date
 openssl ⚠️^0.10.570.10.73maybe insecure
 os_info^3.10.03.11.0up to date
 pasetors^0.7.20.7.4up to date
 pathdiff^0.2.30.2.3up to date
 rand^0.9.00.9.1up to date
 regex^1.11.11.11.1up to date
 rusqlite^0.33.00.36.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.00.9.0up to date
 same-file^1.0.61.0.6up to date
 semver^1.0.251.0.26up to date
 serde^1.0.2171.0.219up to date
 serde-untagged^0.1.60.1.7up to date
 serde_ignored^0.1.100.1.12up to date
 serde_json^1.0.1381.0.140up to date
 sha1^0.10.60.10.6up to date
 shell-escape^0.1.50.1.5up to date
 supports-hyperlinks^3.1.03.1.0up to date
 supports-unicode^3.0.03.0.0up to date
 tar^0.4.430.4.44up to date
 tempfile^3.16.03.20.0up to date
 thiserror^2.0.112.0.12up to date
 time^0.3.370.3.41up to date
 toml^0.8.200.8.22up to date
 toml_edit^0.22.230.22.26up to date
 tracing^0.1.410.1.41up to date
 tracing-chrome^0.7.20.7.2up to date
 tracing-subscriber^0.3.190.3.19up to date
 unicase^2.8.12.8.1up to date
 unicode-width^0.2.00.2.0up to date
 url^2.5.42.5.4up to date
 walkdir^2.5.02.5.0up to date
 windows-sys^0.590.59.0up to date

Dev dependencies

(5 total, 1 outdated)

CrateRequiredLatestStatus
 annotate-snippets^0.11.50.11.5up to date
 cargo-test-support^0.7.10.7.3up to date
 gix^0.70.00.72.1out of date
 same-file^1.0.61.0.6up to date
 snapbox^0.6.210.6.21up to date

Security Vulnerabilities

openssl: Use-After-Free in `Md::fetch` and `Cipher::fetch`

RUSTSEC-2025-0022

When a Some(...) value was passed to the properties argument of either of these functions, a use-after-free would result.

In practice this would nearly always result in OpenSSL treating the properties as an empty string (due to CString::drop's behavior).

The maintainers thank quitbug for reporting this vulnerability to us.