l3montree-dev/devguard

Adjusting the CTA on the Vulnerability Database (Website)

Open

#2,828 opened on Aug 11, 2026

View on GitHubContributor guide
 (0 comments) (0 reactions) (1 assignee)Go (32 forks)auto 404
good first issue

Repository metrics

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

Description

When the issues: #2824 #2825 #2826 #2827 are implemented we should rework the CTA on the DevGuard Vulnerability Website - to ease the conversion from vulnerability Website to the DevGuard Homepage and therefore the DevGuard usage itself.

It could look like something like this: Text and Button under the new features like Vex rules or protection level adjustments "Integrate modern vulnerability management into your Development workflow"

"Looking vulnerability information up costs time, integrate them directly into your Pipelines"

Rounded up with a button to Devguard.org itself.

Contributor guide

Research direction
Inspect the DevGuard vulnerability website project, find the existing CTA component/code, and review the planned features in issues #2824 #2827 to determine how to update the CTA to include text and a button linking to Devguard.org.
Tech stack
go
Domain
frontend
Issue type
Feature
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.
Blocked
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitBasic web development
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80