Pulling information from CVEs to the data, and visualize them in the Bugs dashboard#31
Closed
Pulling information from CVEs to the data, and visualize them in the Bugs dashboard#31
Conversation
…Bugs dashboard Closes #30 Signed-off-by: Alexander Schwartz <alexander.schwartz@ibm.com>
ahus1
force-pushed
the
is-30-add-cves-to-bug-dashboard
branch
from
2295680 to
dbdae20
Compare
stianst
reviewed
Feb 2, 2026
Contributor
stianst
left a comment
stianst
left a comment
There was a problem hiding this comment.
I'm not convinced about this. I don't think CVEs should be mixed together with Bugs, but rather be separate.
CVEs should be sorted in columns based on severity rather than priority like bugs, and each severity should have its own overdue date.
Additional, we most likely want to list issues from keycloak-private, not the CVE-ID or any details, but just the count basically, so that we can have a single view of embargoed and non-embargoed CVEs and what the general status is.
In the end I think it's better to have bugs and CVEs completely separated from each-other, including how they are fetched and stored.
stianst
added a commit
to stianst/keycloak-dashboard
that referenced
this pull request
Feb 18, 2026
Merged
stianst
added a commit
to stianst/keycloak-dashboard
that referenced
this pull request
Feb 18, 2026
Closes keycloak#31 Signed-off-by: stianst <stianst@gmail.com>
Contributor
|
Non-embargoed CVEs added in #34 as a separate table |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
As a first step, show CVEs like any other bug in the bugs dashboard.
The leverages the OR condition introduced in GitHub in 2025.
@stianst - please have a look.
As a follow-up, old CVE data needs to read from GitHub by probably touching all CVEs that don't have a bug label.
Closes #30