## Summary Update the pipeline security tab to use GraphQL & other shared UI components used on the [project](https://gitlab.com/gitlab-org/gitlab/-/security/vulnerability_report), [group](https://gitlab.com/groups/gitlab-org/-/security/vulnerabilities), & [instance ](https://gitlab.com/-/security/vulnerabilities)level vulnerability reports. ## Improvements The pipeline security tab looks the same as the project/group/Security Center vulnerability reports, but it is implemented using entirely different code/endpoints. ## Risks If we do not implement the changes correctly, the pipeline security tab could not work as expected If we have to modify some of the shared components and we do not test it properly, then the vulnerability reports & pipeline security tab may not work as expected. ## Intended side effects - Faster development speed for features that will go on the vulnerability reports and the pipeline security tab: With many new improvements coming to the vulnerability reports, we will want some of these improvements on the pipeline security tab as well; if we do, without this update, we will have to do twice the work. This has already happened in #210327, where two endpoints and UIs needed to be updated to add new columns to the pipeline security tab and the project-level vulnerability reports. - Less files: #223189 aims to remove many unused Vuex files due to the conversion of the security dashboards to GraphQL, but the pipeline security tab still uses many Vuex files; this conversion would allow us to remove many more Vuex files once completed.