No recommendations for how to resolve warnings
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 8.3k
- Forks
- 835
- Avg merge
- 5d 3h
- Merged PRs (30d)
- 1
Description
Bandit reports a lot of "problems" without providing any direction for what kind of code to use instead. Bandit has no capability for detecting when sanitization is used, no whitelist of approved alternatives for the blacklisted methods.
For example, bandit excludes almost every known way to submit an HTTP request, such as the common urllib methods. Well, what should the programmer use instead, the requests package?
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 Bandit's warning-generation and blacklist behavior, then trace how findings are reported for urllib methods. Define the scope for sanitization detection and approved alternatives, including whether requests is an example or a supported recommendation source. Done means the issue has a concrete, maintainable recommendation design and coverage for the affected warnings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devtools, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100