Add CodeQL analysis workflow configuration - #937
Conversation
|
CLA Assistant Lite bot All contributors have signed the CLA ✍️ ✅ |
|
You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool. What Enabling Code Scanning Means:
For more information about GitHub Code Scanning, check out the documentation. |
|
I have read the CLA Document and I hereby sign the CLA |
There was a problem hiding this comment.
Pull request overview
This PR adds a GitHub Actions workflow to enable CodeQL-based SAST scanning in the repository, aligning with the NI Secure Development Lifecycle (SDL) guidance mentioned in the PR description.
Changes:
- Adds a new
.github/workflows/codeql.ymlworkflow for CodeQL “Advanced” analysis. - Configures the workflow to run on pushes/PRs to
masterandUHD-3.9.LTS, plus a weekly scheduled run. - Sets up a language matrix for CodeQL analysis (actions, C/C++, JS/TS, Python).
Comments suppressed due to low confidence (1)
.github/workflows/codeql.yml:94
- The remaining step entries (manual-build and analyze) are also not indented under
steps:. This continues the YAML structure issue and will prevent the workflow from loading.
- name: Run manual build steps
if: matrix.build-mode == 'manual'
shell: bash
run: |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Signed-off-by: Xander Huff <xander.huff@emerson.com>
|
Per Marian Koop, submissions aren't accepted to uhd, directly, but must go to the private uhddev repo first then get integrated over |
Pull Request Details
Per NI Secure Development Lifecycle (SDL) guidance, enable Static Analysis Security Testing (SAST) via CodeQL
Description
Analyzing source code and configuration prior to compilation provides a highly scalable method of security code review and helps ensure that secure policies are being followed. SAST is typically integrated into the commit pipeline to identify vulnerabilities each time the software is built or packaged. However, some offerings integrate into the developer environment to spot certain flaws such as the existence of unsafe or other banned functions and replace those with safer alternatives as the developer is actively coding. Development teams may decide the optimal frequency for performing SAST scans based on the product(s) they develop and may deploy multiple tactics—to balance productivity with adequate security coverage.
Testing Done
None, this was an auto-generated change
Checklist
N/A?