🔍 chore: add CodeQL configuration for security scanning #5700
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR introduces CodeQL security scanning to our repository. It adds a new CodeQL configuration file and a GitHub Actions workflow that automatically runs security analyses on our codebase. These changes aim to proactively detect vulnerabilities and improve the overall security posture of the project.
Changes
.codeql-config.yml
**/test/**
,**/__tests__/**
,**/*.spec.*
, and**/*.test.*
) to focus the analysis on production code..github/workflows/codeql.yml
main
branch, as well as on a scheduled basis (every Friday at 23:43).javascript-typescript
configuration) and performs a security analysis based on our custom configuration.Motivation and Context
Integrating CodeQL into our CI pipeline helps us automatically scan for security vulnerabilities and bugs, ensuring our code remains secure as it evolves. By excluding test files from the analysis, we reduce noise and focus on critical production code. This change aligns with our commitment to security best practices and continuous improvement of our code quality.
Testing
Locally:
CI/CD:
main
branch to trigger the CodeQL workflow.Checklist