Skip to content

ci: enable CodeQL SAST scanning for automated security analysis#5151

Open
RishavTiwari25 wants to merge 2 commits intoboa-dev:mainfrom
RishavTiwari25:ci/add-codeql-sast
Open

ci: enable CodeQL SAST scanning for automated security analysis#5151
RishavTiwari25 wants to merge 2 commits intoboa-dev:mainfrom
RishavTiwari25:ci/add-codeql-sast

Conversation

@RishavTiwari25
Copy link
Contributor

@RishavTiwari25 RishavTiwari25 commented Mar 19, 2026

This Pull Request fixes/closes #5150

It changes the following:

  • Implements a new .github/workflows/codeql.yml workflow using GitHub's native github/codeql-action.
  • Enables automated Static Application Security Testing (SAST) specifically configured for rust to scan the main codebase and newly opened PRs for deeply-nested logical security bugs.
  • Acts as a highly resilient read-only observability layer, pushing located execution flaws, out-of-bounds writes, or logic manipulation alerts straight to the GitHub "Security" tab.
  • Operates totally independently from existing tests and cargo commands, utilizing safe contents: read permissions.

@RishavTiwari25 RishavTiwari25 requested a review from a team as a code owner March 19, 2026 05:22
@github-actions github-actions bot added Waiting On Review Waiting on reviews from the maintainers C-Builtins PRs and Issues related to builtins/intrinsics C-Actions Pull requests that update Github Actions code labels Mar 19, 2026
@github-actions github-actions bot added this to the v1.0.0 milestone Mar 19, 2026
@github-actions github-actions bot removed the Waiting On Review Waiting on reviews from the maintainers label Mar 19, 2026
@github-actions github-actions bot added the Waiting On Review Waiting on reviews from the maintainers label Mar 19, 2026
@github-advanced-security
Copy link

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:

  • The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
  • Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
  • You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

@github-actions
Copy link

Test262 conformance changes

Test result main count PR count difference
Total 52,963 52,963 0
Passed 50,073 50,073 0
Ignored 2,072 2,072 0
Failed 818 818 0
Panics 0 0 0
Conformance 94.54% 94.54% 0.00%

Tested main commit: 055ee0958ce332f3f99af27536a7c6f9a91def27
Tested PR commit: f3e3ffbc8b4057b9d292474a9c725c6f1c7c6f6a
Compare commits: 055ee09...f3e3ffb

@codecov
Copy link

codecov bot commented Mar 19, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 59.51%. Comparing base (6ddc2b4) to head (f3e3ffb).
⚠️ Report is 890 commits behind head on main.

Additional details and impacted files
@@             Coverage Diff             @@
##             main    #5151       +/-   ##
===========================================
+ Coverage   47.24%   59.51%   +12.27%     
===========================================
  Files         476      580      +104     
  Lines       46892    63181    +16289     
===========================================
+ Hits        22154    37602    +15448     
- Misses      24738    25579      +841     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Comment on lines +4 to +7
push:
branches: [ "main" ]
pull_request:
branches: [ "main" ]
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe let's not run this on PRs and pushes. I imagine SASL analysis is a heavy action, so we kinda don't have the CI capacity to run this constantly

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

C-Actions Pull requests that update Github Actions code C-Builtins PRs and Issues related to builtins/intrinsics Waiting On Review Waiting on reviews from the maintainers

Projects

None yet

Development

Successfully merging this pull request may close these issues.

CI: enable CodeQL SAST scanning for automated security analysis

2 participants