Solve vulnerabilities using Pull Requests (PR)
Debricked offers several solutions to tackle open-source vulnerabilities. Learn how to do it using Pull Requests (PR).
Assume we have a repository with loads of vulnerabilities. It will take time to go through each one of them and potentially fix them. Luckily, Debricked offers the ability to open a pull request to solve as many vulnerabilities as possible at once.
Support for pull requests
Currently, we only support pull requests for certain package managers and integrations using the GitHub app, GitLab or Azure DevOps. For information regarding the support of your package manager, check out the language support page.
Solving multiple vulnerabilities using a Pull Request
In a repository, click on Generate pull request to let the tool update your dependencies, in order to solve vulnerabilities, and create a pull request for you
When the pull request is created, you can view in by clicking View generated fix
When the pull request is merged, you will notice a decrease in the number of vulnerabilities.
Set a commit message
Once you press the "Pull Request" button, a new modal is displayed where it is possible to set your own commit message. If you choose not to provide a message, by default the message will be "Fix CVE-XXX" or "Bulk fix vulnerabilities", depending on the type of Pull Request that is created.
Solve a single vulnerability using a Pull Request
It is possible to solve a specific vulnerability in a repository using pull requests, instead of multiple CVEs at once as in the example above.
These are the steps for solving a specific vulnerability:
In a repository, click on the specific vulnerability you wish to remediate
In the CVE view, click the Open pull request button. You can see the vulnerable version(s) and the proposed change
Click on Confirm to execute the changes
If a pull-request is made, creating a new branch, this branch can be viewed in the web tool. If the pull-request is rejected and the branch is deleted, the branch can still be viewed in the UX. This is the case even after a re-scan of the repo, since the branch is still in the database. This data will be pruned only after 30 days.
Last updated
