You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, I semi recently wrote an issue on this repository finding (what I consider to be) a problematic bug in encode_unicode::Utf8Char (#13), and got no response, just checking in to confirm whether or not this crate still has a maintainer behind it for RustSec purposes
(If there is a response within 90 days (soon 270 days I have been told, that will likely be the deadline for this message) from a maintainer stating that this crate is maintained it will be considered maintained, but if there is no response within that timeframe or a maintainer responds that it is indeed not maintained, it will be a candidate for a RustSec unmaintained tag)
I write this because I do not wish for the ecosystem to widely use a crate with a type bug in it, especially if there is no maintainership to triage such bugs or any future bugs
The text was updated successfully, but these errors were encountered:
Hello, I semi recently wrote an issue on this repository finding (what I consider to be) a problematic bug in
encode_unicode::Utf8Char
(#13), and got no response, just checking in to confirm whether or not this crate still has a maintainer behind it for RustSec purposes(If there is a response within 90 days (soon 270 days I have been told, that will likely be the deadline for this message) from a maintainer stating that this crate is maintained it will be considered maintained, but if there is no response within that timeframe or a maintainer responds that it is indeed not maintained, it will be a candidate for a RustSec unmaintained tag)
I write this because I do not wish for the ecosystem to widely use a crate with a type bug in it, especially if there is no maintainership to triage such bugs or any future bugs
The text was updated successfully, but these errors were encountered: