l3montree-dev/devguard

Instance dashboard: Top Vulnerability Projects critical badge not working

Closed

#2,284 opened on Jul 8, 2026

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

Repository metrics

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

Description

The component has a badge that appears when there are critical vulnerabilities in a project and shows their number, but it never shows up (was forced here for this screenshot) because the data from the backend is not accurate. Almost all vulnerabilities are listed as "low", only for one repository while testing there is one "middle" and one "high", but these numbers don't correspond to the actual vulnerability distribution.

This is the vulnResp json that gets sent:

Contributor guide

Research direction
Investigate the backend code that generates the vulnerability response (vulnResp) to understand why vulnerabilities are misclassified as 'low'. Trace the severity mapping logic and check for any data transformation errors.
Tech stack
go
Domain
backend
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
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65