When you visit any website, it may store or retrieve information on your browser, mostly in the form of cookies. This information might be about you, your preferences or your device and is mostly used to make the site work as you expect it to. The information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies. Click on the different category headings to find out more and change our default settings. However, blocking some types of cookies may impact your experience of the site and the services we are able to offer.
More information
.png){kind=logo}
Hello @awolfson (Community Member) ,
The pipeline scan is termed a "pipeline scan" as it only runs on a pipeline, and is usually a quick feedback tool for developers.
For that reason, no PDF can be generated on the platform for that. Is there a reason that you want to send a PDF rather than give the feedback scan findings directly to your developers?
Jason
Veracode Support Engineer
The pipeline scan has capabilities to output to json and if we had a higher GitLab subscription model, that would suffice as the findings would play nicely with SAST reports. Since we don't have a subscription model that supports SAST reports, the json report isn't exactly human-readable and I don't think developers will go to the extent of opening the GitLab jobs to view the console output.
A nice PDF human-readable report would allow for clear visibility.
@awolfson (Community Member) ,
Please take a look at the two links below, as they will help you with flaw import into issues and into the security reports, but please be aware that you would need to have a GitLab Ultimate license to use it to the full extent.
Jason
Veracode Support Engineer