The base implementation of the PDF Vulnerability Report

What does this MR do and why?

Context

We have an epic to build out PDF reporting for our vulnerability_management features.

We previously built a proof of concept, which can be referred to for the decision to use prawn vs other pdf generation strategies. ¹

This Change

The goal of this change is to get all the plumbing in place, so we can start getting pdfs generated and in front of design, to help iterating on the UX and UI.

To that end, this change:

• Adds the skeleton for the specs for individual pdf UI components.
• generates a pdf (containing only the header)
• provides a patch (on the MR) to add a placeholder export button in the UI.
  • patch 0001-Add-UI-button-for-testing.patch

Screenshots or screen recordings

Before	After
	Screencast_from_2025-05-01_01-14-25

How to set up and validate locally

MR acceptance checklist

Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

---

epic: &16989 (closed)
MR: !185058 (merged)
closes: #524055 (closed)
Changelog: added
EE: true

1. The proof of concept MR builds out a demo using the gems. The issue has a writeup on the outcomes of the proof of concept ↩