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 leptos-use

Dependencies

(25 total, 1 possibly insecure)

CrateRequiredLatestStatus
 actix-web^44.10.2up to date
 async-trait^0.10.1.88up to date
 cfg-if^11.0.0up to date
 chrono ⚠️^0.40.4.40maybe insecure
 codee^0.30.3.0up to date
 cookie^0.180.18.1up to date
 default-struct-builder^0.50.5.1up to date
 futures-util^0.30.3.31up to date
 gloo-timers^0.30.3.0up to date
 gloo-utils^0.20.2.0up to date
 http^11.3.1up to date
 js-sys^0.30.3.77up to date
 lazy_static^11.5.0up to date
 leptos^0.70.7.8up to date
 leptos-spin^0.20.2.0up to date
 leptos_actix^0.70.7.8up to date
 leptos_axum^0.70.7.8up to date
 num^0.40.4.3up to date
 paste^11.0.15up to date
 send_wrapper^0.6.00.6.0up to date
 thiserror^22.0.12up to date
 unic-langid^0.90.9.5up to date
 wasm-bindgen^0.2.1000.2.100up to date
 wasm-bindgen-futures^0.40.4.50up to date
 web-sys^0.3.770.3.77up to date

Dev dependencies

(6 total, 2 outdated)

CrateRequiredLatestStatus
 codee^0.30.3.0up to date
 getrandom^0.20.3.2out of date
 leptos_meta^0.70.7.8up to date
 rand^0.80.9.1out of date
 serde^11.0.219up to date
 unic-langid^0.90.9.5up to date

Security Vulnerabilities

chrono: Potential segfault in `localtime_r` invocations

RUSTSEC-2020-0159

Impact

Unix-like operating systems may segfault due to dereferencing a dangling pointer in specific circumstances. This requires an environment variable to be set in a different thread than the affected functions. This may occur without the user's knowledge, notably in a third-party library.

Workarounds

No workarounds are known.

References