ci(security): add CodeQL static analysis workflow for Javascript and Python#219
Open
harmeetsingh11 wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Related Issue
Closes #204
Description
Summary
This pull request introduces a dedicated GitHub CodeQL workflow to enable automated static application security testing (SAST) within the repository's CI pipeline.
The workflow is configured using GitHub's recommended CodeQL actions and provides continuous security analysis for both JavaScript and Python codebases.
Changes Implemented
.github/workflows/codeql.ymlpushevents targeting the default branchpull_requesteventsgithub/codeql-action/initgithub/codeql-action/autobuildgithub/codeql-action/analyzeWhy This Change?
As the repository grows, automated security analysis becomes increasingly important for maintaining code quality and reducing the likelihood of introducing security-related defects.
This workflow provides:
Validation
Expected Outcome
After merging:
Manual Verification
Checklist