Unmaintained and unsound crate: lockfree
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 1.2k
- Forks
- 544
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 45
Description
https://crates.io/crates/lockfree is unmaintained and also unsound (using std::mem::uninitialized). I have tried reaching out to the author of the crate on their gitlab and on github with no success.
It has been much more than the required 90 days. I would like to start the process for issuing a rustsec advisory.
There is a fork from 2023, that I can in no way vouch for: https://crates.io/crates/lock_freedom
References:
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the lockfree crate page and the linked GitLab and GitHub reports first, confirming the unmaintained status and the std::mem::uninitialized issue. Then inspect the advisory-db contribution process; done means the evidence is sufficient for a RustSec advisory and the advisory can be prepared for review.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100