l3montree-dev / l3montree-dev/devguard
Reopen vex rules are recommended if they are created by the organization
Open
Nobody has claimed this yet.
bug
component/devguard-api
- Dominant language
- Go
- Stars
- 161
- Forks
- 43
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 37
Description
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
The issue provides only an attached image and does not name a file, test, or entry point. Start by inspecting the backend code that evaluates VEX rules created by an organization and reproduce the recommendation behavior shown in the image. Done means the intended recommendation behavior for reopened organization-created VEX rules is covered by a test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100