Snyk will test your pull request for vulnerability and license checks in the merge process. This creates an opportunity to establish a security gate and prevent pull requests from adding new vulnerabilities or non-compliant open source libraries that don't meet the license policy of the organization to the source code baseline. The result of the Snyk test check is configurable providing flexibility in the security gate process while minimizing the impact and pace to the software development teams.
In the previous step, we completed the pull request workflow which directed us to the screenshot below. As the PR workflow completed, Snyk validated the vulnerability and license policy set for the project. Based on the policy, the checks either passed or failed and are represented in the GitHub UI.
In the case of our sample application, all checks will pass and we can merge the pull request with the master branch using the merge pull request button.