async-priority-channel is unmaintained, and broken
Open
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://github.com/rmcgibbo/async-priority-channel/issues/75
The objects provided don't meet most definitions of channels (fifo). This is likely to cause someone else to use the library without knowing, and possibly causing a vulnerability.
Developer appears unavailable.
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 reading the linked upstream issue, rmcgibbo/async-priority-channel#75, and then inspect the rustsec/advisory-db contribution conventions. No file, test, or repository entry point is named here, so the expected change and completion criteria need maintainer clarification.
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
- 20/100