What are the recommended language coverage and scanning frequency for CodeQL in a typical GitHub repository using GAS?

Prepare for the GitHub Advanced Security Certification Test. Practice with multiple choice questions, detailed explanations, and hints. Achieve success on your first attempt!

Multiple Choice

What are the recommended language coverage and scanning frequency for CodeQL in a typical GitHub repository using GAS?

Explanation:
Cover all languages used in the repository so CodeQL can analyze every part of the codebase, not just a subset. Running scans on push ensures each new commit is examined for vulnerabilities right away, while scanning on pull requests checks the changes being proposed before they’re merged, catching issues early in the review process. If possible, enabling nightly scans adds a valuable safety net, catching problems that can arise from dependency updates or files that change indirectly, even when there isn’t a new push or PR that day. This approach minimizes gaps in detection and keeps security visibility high across the entire codebase.

Cover all languages used in the repository so CodeQL can analyze every part of the codebase, not just a subset. Running scans on push ensures each new commit is examined for vulnerabilities right away, while scanning on pull requests checks the changes being proposed before they’re merged, catching issues early in the review process. If possible, enabling nightly scans adds a valuable safety net, catching problems that can arise from dependency updates or files that change indirectly, even when there isn’t a new push or PR that day. This approach minimizes gaps in detection and keeps security visibility high across the entire codebase.

Subscribe

Get the latest from Passetra

You can unsubscribe at any time. Read our privacy policy