Is this crate still maintained?

[Moxinilian]

A panic safety issue has been pointed out in #90 four months ago, a fix was offered in #91 three months ago but has still not been merged, the crate has last received a new commit two years ago and the maintainer seems inactive.

Is this crate still maintained?

[LiquidityC]

I've also been wondering. If this project needs an additional maintainer I would be prepared to help out with the "critical" issues. Eg. No new features but maintaining the dependencies and security patches just to keep it running. A lot of the rust echo system has dependencies on this crate.

[LiquidityC]

I've started prepping my fork for a potential fork-release of this project and merged my security PR into the codebase. Take a look here: https://github.com/LiquidityC/slice_ring_buffer

This is the first time I've had to deal with something like this so if anyone has some time and investment in this fork please take a look and come with suggestions.

I aim to put the minimal amount of work into the codebase once I have all the CI steps setup. If you want to be included among contributors that would be fine too.

[Boscop]

This crate had so much potential, but is unmaintained now :/
Is there any fork that is maintained and has the PRs merged?

[LiquidityC]

This crate had so much potential, but is unmaintained now :/ Is there any fork that is maintained and has the PRs merged?

As mentioned above I created this fork: https://github.com/LiquidityC/slice_ring_buffer

No active development but I'm prepared to handle security PRs etc.