Soundness issues for `futures-intrusive`
Open
Nobody has claimed this yet.
Unmaintained
Unsound
- Dominant language
- No language data
- Stars
- 1.2k
- Forks
- 544
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 45
Description
I stumbled over two soundness issues of futures-intrusive which are currently unfixed.
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
Start by reviewing the two referenced futures-intrusive issues, 42 and 56, to understand the reported soundness problems and their current status. The issue does not identify files, tests, or the expected advisory-db change, so confirm with maintainers whether advisory entries are needed and what completion should mean.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100