Ensure that each #nosec usage has an accompanying explanation
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Python
- Stars
- 8.3k
- Forks
- 835
- Avg merge
- 5d 3h
- Merged PRs (30d)
- 1
Description
Transfer of OpenStack blueprint:
https://blueprints.launchpad.net/bandit/+spec/nosec-has-comment
#nosec tags should not just be used to make problems go away. Every time somebody uses #nosec it should be accompanied by an explanation for why this really isn't a security issue.
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 the linked Launchpad blueprint and searching the Bandit repository for #nosec handling and existing tests. Trace how #nosec tags are parsed and reported, then define completion as every such usage requiring and validating an accompanying explanation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devtools, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100