-
Notifications
You must be signed in to change notification settings - Fork 114
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
Is this crate still maintained? #185
Comments
7 tasks
7 tasks
I've created a fork under a new name, and I'll start trying to (slowly, probably) work my way through the open PRs. |
It seems like all the issues mentioned above have been closed. So what's the status of this? It seems that it can be closed? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This crate seems to be completely abandoned. There are many unfixed critical bugs (#124, #143, #152, #154) as well as missing important dependency security updates (#179).
Last commit was 3f4e01a (Jul 27, 2020) and last release was v15.0.0 (May 15, 2020).
It may be a good idea to ask for maintenance support from the community. In the meaning time, I will submit an entry to RustSec advisory db to reflect the current state of this crate (rustsec/advisory-db#891).
The text was updated successfully, but these errors were encountered: