Is there a bug in chrono 0.0.0-0?

Potential segfault in `localtime_r` invocations ### 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 - [time-rs/time#293](https://github.com/time-rs/time/issues/293) Fixed in chrono 0.4.20.

This package has limited bug data (1 entry). Check back later or see the package health page for the full signal.

chrono known bugs

cargo

1 known bug in chrono, with affected versions, fixes and workarounds. Sourced from upstream issue trackers.

View package health \u2192 Breaking changes \u2192

bugs

Known bugs

Severity	Affected	Fixed in	Title	Status	Source
medium	0.0.0-0	0.4.20	Potential segfault in `localtime_r` invocations ### 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 - [time-rs/time#293](https://github.com/time-rs/time/issues/293)	fixed	osv:RUSTSEC-2020-0159

API access

Get this data programmatically \u2014 free, no authentication.

curl https://depscope.dev/api/bugs/cargo/chrono