-
Notifications
You must be signed in to change notification settings - Fork 33
RUSTSEC-2019-0031: spin is no longer actively maintained #2189
Comments
We don't use these features and they bring in unmaintained dependencies: #2189
Output of
Once that is merged, we will need to wait for libp2p to update the newest version of ring. Given that libp2p is currently tracking the latest one, I would assume they will update fast. We also need |
2194: Remove libp2p-websocket and secp256k1 dependencies r=mergify[bot] a=thomaseizinger We don't use these features and they bring in unmaintained dependencies: #2189 Co-authored-by: Thomas Eizinger <[email protected]>
What would |
We currently use the |
Am I understanding it correctly that there is nothing to do for us? |
There is nothing we can do (yet) yes. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
Seems this PR might never leave draft, from the advisory page:
We might have to tackle this different than waiting. @thomaseizinger |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
spin
0.5.2
The author of the
spin
crate does not have time or interest to maintain it.Consider the following alternatives (both of which support
no_std
):conquer-once
lock_api
(a subproject ofparking_lot
)See advisory page for additional details.
The text was updated successfully, but these errors were encountered: