Code scanning
To find vulnerabilities in your own code, you can use Static Application Security Testing (SAST). SAST is considered white-box testing, as it has full access to the source code. It is not a pure static code analysis, as that normally includes building software. But unlike Dynamic Application Security Testing (DAST) – we will learn more about that in Chapter 15, Securing Your Deployments – it is not executed at runtime but at compile time.
Code scanning in GitHub
In GitHub, SAST is called code scanning, and it is available for all public repositories and for private repositories that have GitHub Advanced Security enabled. You can use code scanning with all tools that support the Static Analysis Results Interchange Format (SARIF). SARIF is an OASIS Standard based upon JSON that defines the output format for static analysis tools. GitHub code scanning currently supports SARIF 2.1.0, which is the newest version of the standard (see https://docs.github...