Repository navigation
ci: add Python and Actions CodeQL security scanning - #4974
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
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. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 2e58b4a526
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
@codex review Please review exact head The cooldown finding has an evidence-backed reply: #4964 already added the documented seven-day GitHub Actions cooldown on the target branch. The target and PR merge both contain it; GitHub documents that security updates bypass cooldown. Please assess whether any supported blocker remains in the one-file CodeQL change using that effective configuration. No new code was necessary, and all 22 exact-head checks remain green. |
HAYDEN-OAI
left a comment
There was a problem hiding this comment.
Reviewed the complete 43-line workflow addition at 2e58b4a526bb10b47c7196b9d98ec517d0b266bd against merge base faf10fda7cd68bebdfba5edb887a0805cd1c9464. No substantive introduced defects found.
The main push/PR/weekly triggers, separate Python and Actions analyses/categories, pinned official actions, no-build analysis, non-persistent checkout credentials, and narrowly scoped upload permissions fit the intended security-scanning boundary without changing existing workflows.
The workflow correctly distinguishes successful analysis execution from findings-based protection. Requiring both language jobs and configuring native CodeQL protection with both severity thresholds set to All remain separate administrator steps; GitHub documents the PR-diff and merge-group limitations. This approval does not certify deployed enforcement or clear scanner findings. Repository-admin settings were not independently verified.
The earlier Actions cooldown concern is covered on current main by #4964, which adds the seven-day ordinary-update cooldown; this PR does not alter that configuration.
Static review only; I did not run or assess tests, CI, or mergeability.
|
Codex Review: Didn't find any major issues. Another round soon, please! Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
🛡️ Codex Security Review · Automatically triggeredSecurity review completed. No security issues were found in this pull request. Reviewed commit: Only the user who started this review can view the report in Codex. ℹ️ About Codex security reviews in GitHubThis is an experimental Codex feature. Security reviews are triggered when:
Once complete, Codex will leave suggestions, or a comment if no findings are found. |
This pull request adds CodeQL security scanning for Python and GitHub Actions on main pushes, main-targeted pull requests, and a weekly schedule. The repository currently has no configured CodeQL security analysis; its separate Code Quality workflow does not establish security coverage.
Summary
CodeQL (python)andCodeQL (actions)jobs with immutable official action pins, separate result categories, and no-build analysis.Deployment follow-up
Administrators must preserve existing required checks, require both new language jobs, and activate native CodeQL merge protection on main with Alerts: All and Security alerts: All. Verify real main/PR/fork/Dependabot/scheduled runs, processed results, initial-alert triage, and effective enforcement after deployment. These settings are not changed by this PR.
Native findings protection covers PR-diff findings and excludes merge groups. No merge queue is introduced.
Test plan