build(deps): Update pyyaml requirement from >=6.0 to >=6.0.3 #276
security-scans.yaml
on: pull_request
Dependency Review
6s
Shell Script Lint
7s
YAML Lint
7s
Python Security (Bandit)
10s
Dockerfile Lint (Hadolint)
9s
Trivy Filesystem Scan
30s
Verify Action Pinning
5s
Matrix: codeql
Annotations
4 errors and 9 warnings
|
Dockerfile Lint (Hadolint):
authbridge/cmd/authbridge/Dockerfile.light#L23
DL3003 warning: Use WORKDIR to switch to a directory
|
|
Dockerfile Lint (Hadolint):
authbridge/cmd/authbridge/Dockerfile#L25
DL3003 warning: Use WORKDIR to switch to a directory
|
|
Dockerfile Lint (Hadolint):
authbridge/authproxy/Dockerfile.authbridge#L23
DL3003 warning: Use WORKDIR to switch to a directory
|
|
Dockerfile Lint (Hadolint):
authbridge/authproxy/Dockerfile.authbridge#L18
DL3003 warning: Use WORKDIR to switch to a directory
|
|
Verify Action Pinning
Found actions not pinned to SHA commits:
|
|
Dependency Review
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/dependency-review-action@2031cfc080254a8a887f58cffee85186f0e49e48. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
YAML Lint:
.github/workflows/project.yml#L24
24:1 [empty-lines] too many blank lines (1 > 0)
|
|
YAML Lint:
.github/workflows/build.yaml#L118
118:151 [line-length] line too long (189 > 150 characters)
|
|
Trivy Filesystem Scan
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
CodeQL Analysis (python)
Starting April 2026, the CodeQL Action will skip computing file coverage information on pull requests to improve analysis performance. File coverage information will still be computed on non-PR analyses.
To opt out of this change, set the `CODEQL_ACTION_FILE_COVERAGE_ON_PRS` environment variable to `true`. Alternatively, create a custom repository property with the name `github-codeql-file-coverage-on-prs` and the type "True/false", then set this property to `true` in the repository's settings.
|
|
CodeQL Analysis (python)
1 issue was detected with this workflow: Please specify an on.push hook to analyze and see code scanning alerts from the default branch on the Security tab.
|
|
CodeQL Analysis (go)
Starting April 2026, the CodeQL Action will skip computing file coverage information on pull requests to improve analysis performance. File coverage information will still be computed on non-PR analyses.
To opt out of this change, set the `CODEQL_ACTION_FILE_COVERAGE_ON_PRS` environment variable to `true`. Alternatively, create a custom repository property with the name `github-codeql-file-coverage-on-prs` and the type "True/false", then set this property to `true` in the repository's settings.
|
|
CodeQL Analysis (go)
1 issue was detected with this workflow: Please specify an on.push hook to analyze and see code scanning alerts from the default branch on the Security tab.
|