[tblauvvik]

Adds CodeQL code scanning through the shared reusable workflow in OriginAS/origin-actions (push to the default branch, pull requests, monthly schedule).

What it does

Trigger	When
push	to main
pull_request	opened, synchronize, reopened, ready_for_review (drafts are skipped)
schedule	monthly, the 1st at 05:00 UTC
workflow_dispatch	manual run

• JDK: not set. There is no pom.xml, so the input is left at its default and Maven is not configured.
• Languages: auto-detected (expected: GitHub Actions). Queries: security-extended.
• Secrets: secrets: inherit (the optional package token is only used by Maven projects).
• Permissions: security-events: write only on the analyze job.

Before merging

• CodeQL default setup must stay off for this repo, otherwise GitHub rejects these uploads.

After merge

• The push to main starts the first full scan (Security → Code scanning). Nothing deploys.

🤖 Generated with Claude Code

[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.