Skip to content

CodeQL

CodeQL #750

Triggered via schedule October 20, 2024 02:43
Status Failure
Total duration 1m 39s
Artifacts

codeql.yml

on: schedule
Fit to window
Zoom out
Zoom in

Annotations

1 error and 11 warnings
🏭 Scanning
Resource not accessible by integration
🏭 Scanning
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
🏭 Scanning
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, github/codeql-action/init@v2, github/codeql-action/analyze@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
🏭 Scanning
CodeQL Action v2 will be deprecated on December 5th, 2024. Please update all occurrences of the CodeQL Action in your workflow files to v3. For more information, see https://github.blog/changelog/2024-01-12-code-scanning-deprecation-of-codeql-action-v2/
🏭 Scanning
Resource not accessible by integration
🏭 Scanning
This run of the CodeQL Action does not have permission to access Code Scanning API endpoints. As a result, it will not be opted into any experimental features. This could be because the Action is running on a pull request from a fork. If not, please ensure the Action has the 'security-events: write' permission. Details: Resource not accessible by integration
🏭 Scanning
Feature flags do not specify a default CLI version. Falling back to the CLI version shipped with the Action. This is 2.19.1.
🏭 Scanning
Resource not accessible by integration
🏭 Scanning
Resource not accessible by integration
🏭 Scanning
Resource not accessible by integration
🏭 Scanning
Resource not accessible by integration
🏭 Scanning
Resource not accessible by integration