[Oct4Pie]

Code scanning ran through GitHub's default setup, which only covered Actions and Python. The app and the privileged helper are Swift, so most of the code that matters was never scanned.

This replaces the default setup with a workflow that runs the same Actions and Python analysis and adds Swift. The Swift job builds the app and helper unsigned on a macOS runner so CodeQL can trace the compiled code. The tracer runs xcodebuild under Rosetta, so the build targets a generic Mac, and packages are fetched before tracing starts. It runs on pull requests to main, on pushes to main and once a week.

The first scan flagged that CI jobs ran with the default token permissions, so CI now gets a read-only token.

The default setup has been switched off in the repository settings, because GitHub refuses results from a workflow while the default setup is on.

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