Informationen zu code scanning
With code scanning, developers can quickly and automatically analyze the code in a GitHub repository to find security vulnerabilities and coding errors.
You can use code scanning to find, triage, and prioritize fixes for existing problems in your code. Code scanning also prevents developers from introducing new problems. You can schedule scans for specific days and times, or trigger scans when a specific event occurs in the repository, such as a push.
If code scanning finds a potential vulnerability or error in your code, GitHub displays an alert in the repository. Nachdem Du den Code korrigiert hast, der die Meldung ausgelöst hat, schließt GitHub die Meldung. For more information, see "Managing code scanning alerts for your repository."
To monitor results from code scanning across your repositories or your organization, you can use webhooks and the code scanning API. For information about the webhooks for code scanning, see "Webhook events and payloads." For information about API endpoints, see "Code scanning."
To get started with code scanning, see "Setting up code scanning for a repository."
Informationen zu CodeQL
Code scanning uses GitHub Actions. CodeQL treats code as data, allowing you to find potential vulnerabilities in your code with greater confidence than traditional static analyzers.
QL is the query language that powers CodeQL. QL is an object-oriented logic programming language. GitHub, language experts, and security researchers create the queries used for code scanning, and the queries are open source. The community maintains and updates the queries to improve analysis and reduce false positives. For more information, see CodeQL on the GitHub Security Lab website.
For more information about API endpoints for code scanning, see "Code scanning."
- C/C++
- C#
- Go
- Java
- JavaScript/TypeScript
- Python
You can view and contribute to the queries for code scanning in the github/codeql repository. For more information, see CodeQL queries in the CodeQL documentation.
Informationen zur Abrechnung für code scanning
Code scanning uses GitHub Actions, and each run of a code scanning workflow consumes minutes for GitHub Actions. Weitere Informationen findest Du unter „Informationen zur Abrechnung für GitHub Actions.“
About third-party code scanning tools
Code scanning ist mit Code-Scan-Werkzeugen von Drittanbietern interoperabel, welche SARIF-Daten (Static Analysis Results Interchange Format) ausgeben. SARIF ist ein Open-Source-Standard. Weitere Informationen findest Du unter „SARIF-Ausgabe für code scanning."
You can run third-party analysis tools within GitHub using actions or within an external CI system. For more information, see "Setting up code scanning for a repository" or "Uploading a SARIF file to GitHub."
Weiterführende Informationen
- "Securing your repository"
- GitHub Security Lab
- OASIS Static Analysis Results Interchange Format (SARIF) TC on the OASIS Committee website