CI: run new rules against a set of well-known files to demonstrate prevalence
Open
Nobody has claimed this yet.
CI
enhancement
performance
usability
- Dominant language
- Python
- Stars
- 6.2k
- Forks
- 726
- Avg merge
- 11d 11h
- Merged PRs (30d)
- 7
Description
shows if a rule is susceptible to obvious FPs or unexpected matches. doesn't need to be a huge scale of samples, just a bit of diversity.
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
No files or tests are named. Start by locating the CI configuration and rule-test entry point, then identify a small, diverse set of well-known files; done means new rules run against them and the results expose obvious false positives or unexpected matches.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- ci-cd, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100