Repository navigation
Add CodeQL scanning and harden workflows - #505
Open
nachocodoner wants to merge 2 commits into
Open
nachocodoner wants to merge 2 commits into
nachocodoner wants to merge 2 commits into
Conversation
|
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. |
nachocodoner
marked this pull request as ready for review
November 5, 2026 12:35
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.
Add CodeQL scanning and address the workflow hardening findings from the initial baseline.
Set the integration-test workflow to read-only contents access and pin the existing Meteor setup action ref.
CodeQL covers JavaScript/TypeScript and GitHub Actions on the configured mainline branches, weekly and by manual dispatch. The existing query suite and extraction scope are unchanged. Permission changes retain required job access, and action pins resolve existing refs without version upgrades. Commands, triggers and application source are unchanged.
Validation: full branch rescan passed at
9d806c9563c28d5c3d9d36acac5469a6ace2b38b, with both upload categories and unrestricted query execution verified. Workflow findings fell from 1 to 0; 0 JavaScript/TypeScript findings remain for triage. No alerts were dismissed.PR delta validation: CodeQL PR scan passed at the same amended head, with zero results in both JavaScript/TypeScript and Actions. Logs verify the PR diff-range extension was used, and uploaded analyses match the merge of this head with the target branch. The full branch rescan above independently confirms the targeted workflow findings are absent; remaining source findings stay in triage.
YAML comparison confirms only permissions and action refs changed. Whitespace checks passed with existing line endings preserved. Actionlint introduced no new diagnostics.
Existing CI: Meteor CI success.
Review remaining findings and coverage, then verify mainline scanning after merge.