[dDevAhmed]

Summary

Implements CLI-012 with CodeQL scanning for the StellarForge CLI JavaScript/TypeScript codebase.

Included

• CodeQL analysis on every pull request
• CodeQL analysis on pushes to main
• weekly scheduled scan
• javascript-typescript language configuration with build mode none
• CodeQL Action v4.37.6 pinned to immutable commit 5595ccaf912efad79be6eef63a5619ff05969be3
• Checkout v7.0.1 remains pinned and does not persist credentials
• security guidelines updated with alert triage/ownership expectations

Permissions / security

• contents: read
• security-events: write only for SARIF/code-scanning result upload
• no repository-content write permission
• no secrets
• no pull_request_target
• no execution of package install scripts or project build hooks in the CodeQL workflow
• PR code is analyzed in the normal unprivileged pull_request context

Schedule

The scheduled scan runs weekly on Wednesday at 04:17 UTC. The non-round minute intentionally avoids the busiest top-of-hour schedule window.

Findings ownership

New CodeQL findings are maintainer-owned security work. Findings must be triaged for validity, reachability, severity, and affected trust boundaries; dismissals should carry reviewable rationale.

Closes #15

[github-advanced-security]

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.