Clarification: 1.3.12 "sanitized"
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 3.6k
- Forks
- 831
- Avg merge
- 7h 55m
- Merged PRs (30d)
- 4
Description
1.3.12 Verify that regular expressions are free from elements causing exponential
backtracking, and ensure untrusted input is sanitized to mitigate ReDoS or
Runaway Regex attacks
Use “escaped or strictly validated” instead of “sanitized,” and mention input length and resource limits. Also add guidance to use safe regex engines or good libraries/tools.
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
Search the raw .md files in the 5.0 branch for requirement 1.3.12. Review the current wording, then update it to use “escaped or strictly validated,” cover input length and resource limits, and mention safe regex engines or libraries/tools. Done means the requirement includes all requested guidance in the master Markdown source.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, security
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100