Skip to content
GitLab
Next
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    Projects Groups Topics Snippets
  • Register
  • Sign in
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 51,814
    • Issues 51,814
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,570
    • Merge requests 1,570
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • GitLabGitLab
  • Issues
  • #357300
Closed
Open
Issue created Mar 30, 2022 by Sam White@sam.whiteDeveloper

Remove Vulnerability-Check

Proposal

All code related to Vulnerability-Check will be removed from the product.

  1. Documentation about Vulnerability-Check
    1. https://docs.gitlab.com/ee/user/application_security/#vulnerability-check-rule should be replaced with a reference to scan result policies
    2. The deprecation notice at https://docs.gitlab.com/ee/api/merge_request_approvals.html#create-project-level-rule
    3. The deprecation notice at https://docs.gitlab.com/ee/api/merge_request_approvals.html#update-project-level-rule
  2. APIs related to Vulnerability-Check
    1. Note: I do not believe there is any work to do here, but it would be good to double check. The most likely place is in the accepted values for [ApprovalRule.sourceRule](https://docs.gitlab.com/ee/api/graphql/reference/#approvalrule) and [ApprovalRule.type](https://docs.gitlab.com/ee/api/graphql/reference/#approvalrule)
  3. Frontend code related to Vulnerability-Check in the Settings > General > Merge Request Approvals page
  4. Frontend code related to Vulnerability-Check in the MR page
  5. All backend code related to Vulnerability-Check
Edited May 12, 2022 by Zamir Martins
Assignee
Assign to
Time tracking