<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Label this issue](https://contributors.gitlab.com/manage-issue?action=label&projectId=278964&issueIid=591068) </details> <!--IssueSummary end--> ## Overview :information_source: Please note the use the `ee/` in directories and `EE` in code because [advisory data is GitLab EE only feature](https://handbook.gitlab.com/handbook/product/categories/features/#vulnerability-research). This work item covers creating `ee/app/graphql/types/package_metadata/advisory_type.rb` along with tests. This GraphQL type will represent the `ee/app/models/package_metadata/advisory.rb` model. ## Actions - [x] Create `ee/app/graphql/types/package_metadata/advisory_type.rb` (you'll need to create the `ee/app/graphql/types/package_metadata` directory first). - [ ] ~~Ensure we consider [limiting maximum field call count](https://docs.gitlab.com/development/api_graphql_styleguide/#limit-maximum-field-call-count) (if appropriate).~~ _Not applicable here_ - [x] Create `spec/graphql/types/package_metadata/advisory_type_spec.rb` to fully test `ee/app/graphql/types/package_metadata/advisory_type.rb`. - [x] Ensure GraphQL query returns complete advisory information (severity, description, CVSS scores, identifiers) for queried CVE IDs. <!--template sourced from https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Default.md-->