ci(security): Set up code scanning

[AaronDewes]

This sets up CodeQL to automatically detect possible security problems.

[github-advanced-security]

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.

[AaronDewes]

It appears it only detected 3 instances of the same issue in tests. I'll create a separate PR to fix these for the beta branch. It's not a real vulnerability, so there's nothing important to fix here, but it's still good to have some automated monitoring.

[Uzlopak]

I think there is an option for making a "deep" scan.

[AaronDewes]

I think there is an option for making a "deep" scan.

Not sure what you mean by deep scan? Do you mean the extended rules? https://docs.github.com/en/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/customizing-your-advanced-setup-for-code-scanning#using-queries-in-ql-packs

GitHub Docs

Customizing your advanced setup for code scanning - GitHub Docs

You can customize how your advanced setup scans the code in your project for vulnerabilities and errors.

[Uzlopak]

yes. security-and-quality

[AaronDewes]

I was going to try the "simple" setup first, but we can probably really move to that.

[Uzlopak]

LGTM

[github-actions]

🎉 This PR is included in version 13.0.0-beta.4 🎉

The release is available on:

• GitHub release
• npm package (@beta dist-tag)

Your semantic-release bot 📦🚀