PDF v2: structured CVE Findings table (#167) - #234
Merged
Conversation
Replaces reliance on raw vulners script dumps: adds a recursive XSLT walker that parses the vulners @output into a structured CVE Findings table on page 1 - CVE ID (hyperlinked to vulners.com), host/port context, and reference columns. Verified against a real scan: 26 CVEs rendered as a proper table, PDF regenerated through the app's Playwright converter (6 pages), table renders on page 1 below the severity summary.
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
This was referenced Aug 22, 2026
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
1 participant
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.
Part of #167 v2 (PDF usability for client-facing reports).
Change
Adds a structured CVE Findings table to the PDF report, replacing the current approach where CVEs are only visible buried inside raw vulners script output on pages 4-5.
@outputline-by-lineVerification
Known limitation
CVE title/description column truncates at page edge (same wide-table issue noted in #230 follow-up); full details remain available via the hyperlinked IDs.