-
Notifications
You must be signed in to change notification settings - Fork 377
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
*ring* is unmaintained #2227
Comments
Sad to hear, but grateful for your work on |
@briansmith looking at briansmith/ring#2414 it sounds like you want to put the project in a state we would normally describe as “passively maintained”. If you still want to file this advisory out of caution because there may be delays in e.g. addressing security vulnerability reports, we can do it, but I wanted to make sure you want to go through with this even though it’s a bit outside our normal criteria for “unmaintained” crates. |
Thanks Tony. I edited my statement in the thread you linked to be a little clearer. It is best to have it marked "unmaintained" in the advisory DB and I would like this to happen ASAP. |
I've opened a PR to add an advisory here: #2228 |
* Add unmaintained advisory for *ring* See #2227 * Fix crate name --------- Co-authored-by: Sergey "Shnatsel" Davidoff <[email protected]>
The advisory is live as RUSTSEC-2025-0007 |
No description provided.
The text was updated successfully, but these errors were encountered: