Is `nix` issue 1040 worth an informational warning?
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/nix-rust/nix/issues/1040 argues that an API in the nix crate is unsound. I don't understand Unsafe Rust myself, so I'd like to ask: do you think it's worth an informational = "unsound" warning in the advisory-db?
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 nix issue 1040 and the surrounding discussion about whether the nix crate API is unsound. Then review how rustsec/advisory-db represents informational unsoundness warnings; done means reaching a documented decision about whether this case belongs in the advisory database.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100