`mbox` is unmaintained and unsound
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/kennytm/mbox
https://crates.io/crates/mbox
Last commit on 2021-04-01
Last release on 2021-04-01
The author is not responding.
Unsoundness: https://github.com/kennytm/mbox/issues/23
2 reverse dependencies on crates.io
140 (transitive) dependents on github
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 mbox crate page and the linked unsoundness issue, then inspect how this advisory database records reports for unmaintained or unsound crates. Done means the repository has an appropriate advisory record for mbox that reflects the reported evidence and affected dependents.
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
- Needs clarification
- Newbie friendliness
- 35/100