-
-
Notifications
You must be signed in to change notification settings - Fork 152
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Vulnerable dependency: time brought in via chrono #226
Comments
Waiting on chronotope/chrono#578 |
chrono itself is also considered vulnerable: https://rustsec.org/advisories/RUSTSEC-2020-0159 |
The PR still seem to not be merged. Could a potential move to the |
I've opened #241 to at least remove the time 0.1 dependency |
I would like to remove the chrono dependency, I think migrating to time is feasible now |
Closing this in favor of removing chrono for time 0.3 |
Hi there!
The crate
time
before0.2.23
has a vulnerability, more info here: https://github.com/RustSec/advisory-db/blob/main/crates/time/RUSTSEC-2020-0071.mdFYI
time
is brought in viachrono
to this project.I've made a comment on a
chrono
issue where they are discussing upgrading time: chronotope/chrono#553 (comment)I imagine you can't do too much until
chrono
updates, but pointing this out seemed like a good idea!Cheers,
Jeffry
cc @bhamail
The text was updated successfully, but these errors were encountered: