Outline which variables allow untrusted input.
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 2k
- Forks
- 135
- PR merge metrics
- No merged PRs in 30d
Description
I think it'd be useful if it the docs made it obvious which fields can have untrusted input in them, because otherwise users might set themselves up for injection attacks.
Contributor guide
No contributing guide indexed for this repository
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 library's public API documentation and identify which fields can receive untrusted input. Document those inputs and the associated injection risk so users can recognize them before configuring the library.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- documentation, security
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100