l3montree-dev/devguard

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

Open

#2,114 opened on Jun 10, 2026

View on GitHub
 (3 comments) (0 reactions) (1 assignee)Go (32 forks)auto 404
component/devguard-webgood first issueusability

Repository metrics

Stars
 (144 stars)
PR merge metrics
 (PR metrics pending)

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.

Contributor guide

Research direction
Implement a 'Reapply' button and update the label to 'Matching Rules' in the vulnerability details UI when a vulnerability is reopened after being marked as a false positive.
Tech stack
None
Domain
frontend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75