l3montree-dev / l3montree-dev/devguard

Missing "Reapply" Button and Incorrect Label "Applied Rules" for Reopened Vulnerabilities

Open
#2,114 3 comments 0 reactions 1 assignee View on GitHub

@JagadeeshChandra12 is already working on this.

Since Jun 10, 2026.

component/devguard-web good first issue usability
Dominant language
Go
Stars
161
Forks
43
Avg merge
1d 8h
Merged PRs (30d)
37

Description

Summary
When a vulnerable package is marked as a false positive and subsequently reopened, the UI is missing a "Reapply" button and displays an incorrect section label.

Current Behavior

  • The section is labeled "Applied Rules", even though the rule has not been (re)applied after reopening.
  • There is no "Reapply" button available, leaving the user with no clear action to re-trigger the rule.

Expected Behavior

  • The label should read "Matching Rules" to accurately reflect that the rule matches the given path but has not yet been applied. Making it clear to the user that action is still required.
  • A "Reapply" button should be present, allowing the user to explicitly reapply the rule after reopening the vulnerability.

Steps to Reproduce

  • Identify a vulnerable package with an applied rule (e.g., marked as false positive).
  • Reopen the vulnerability.
  • Observe the UI — the label still reads "Applied Rules" and no "Reapply" button is shown.
Image

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.