-
-
Notifications
You must be signed in to change notification settings - Fork 63
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
Maintenance status? #435
Comments
There's been an update on the maintenance status here: #432 (comment) I think rustsec unmtaintained entries often do more harm than good, see Armin Ronacher's recent article for instance. |
Hi there! Yes, depending on how you define "unmaintained", you might consider Isahc temporarily unmaintained. Due to just my life circumstance at the moment, I have very little time to work on Isahc, and am much more likely to spend that little time I have elsewhere. There is a plan for a version 2.0, but there's still quite a bit of remaining work to get it done, and I am not working on that right now. However, if an actual security vulnerability or notable bug were to be reported on 1.x, I would scrape up the time to address it in a timely manner to the best of my ability. There have not been any such issues recently, so there hasn't been any repo activity. |
It seems this crate has not seen activity in the past two years (last commit 2022-11-07). What is the maintenance status?
Ping @sagebind. If this crate is not maintained any longer it would be good to state so.
I opened RustSec advisory-db issue (rustsec/advisory-db#1954) and I can file unmaintained advisory there if needed.
The text was updated successfully, but these errors were encountered: