l3montree-dev/devguard

Locked by vex rule even though i handled the vulnerability without any rule

Open

#2,767 opened on Aug 4, 2026

View on GitHubContributor guide
 (0 comments) (0 reactions) (1 assignee)Go (32 forks)auto 404
bugcomponent/devguard-webgood first issue

Repository metrics

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

Description

This issue does not include a description.

Contributor guide

Research direction
Investigate how VEX rules trigger locking of vulnerabilities and reproduce the scenario described in the screenshot. Trace the code path that processes VEX rules and the handling of vulnerabilities without any rule to determine why it becomes locked.
Tech stack
go
Domain
backendsecurity
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Needs investigation
Prerequisites
GitGo
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30