How to add Static Application Security Testing (SAST) with SonarQube Cloud Free Tier to a GitLab CI/ CD pipeline

ESLint catches code quality issues. Typecheckers ensures variables and functions use the correct data types. Prettier automatically formats code for consistent style. But how can we start incorporating security testing into this GitLab CI/CD pipeline we have built? GitLab repo: https://gitlab.com/tjmaher/bun-create-playwrightFor this blog post we will be looking at one way to do Static Application Security Testing (SAST), adding SonarQube to our project.What is Static Application Security Testing?Static Application Security Testing (SAST) is a method of security testing that scans an application's source code, bytecode, and binaries for any security flaws. Because it analyzes the code without actually running the application -- meaning the code is "static" -- developers can use it early in the coding phase to catch and fix bugs immediately.Although source code scanners have been around a while in the computer industry, the term "Static Application Security Testing (SAST)" originated…