chore(processesworker): fix workflow trigger #23
Annotations
12 warnings
|
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, github/codeql-action/upload-sarif@v2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
|
Upload SARIF file for GitHub Advanced Security Dashboard
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/
|
|
KICS scan:
charts/ssi-credential-issuer/templates/deployment-issuer-service.yaml#L39
Check if containers are running with low UID, which might cause conflicts with the host's user table.
|
|
KICS scan:
charts/ssi-credential-issuer/templates/cronjob-issuer-processes.yaml#L37
Check if containers are running with low UID, which might cause conflicts with the host's user table.
|
|
KICS scan:
charts/ssi-credential-issuer/templates/cronjob-expiry-app.yaml#L37
Check if containers are running with low UID, which might cause conflicts with the host's user table.
|
|
KICS scan:
charts/ssi-credential-issuer/templates/cronjob-expiry-app.yaml#L37
Containers should be configured with a secure Seccomp profile to restrict potentially dangerous syscalls
|
|
KICS scan:
charts/ssi-credential-issuer/templates/cronjob-issuer-processes.yaml#L37
Containers should be configured with a secure Seccomp profile to restrict potentially dangerous syscalls
|
|
KICS scan:
charts/ssi-credential-issuer/templates/deployment-issuer-service.yaml#L39
Containers should be configured with a secure Seccomp profile to restrict potentially dangerous syscalls
|
|
KICS scan:
charts/ssi-credential-issuer/templates/cronjob-issuer-processes.yaml#L35
Service Account Tokens are automatically mounted even if not necessary
|
|
KICS scan:
charts/ssi-credential-issuer/templates/deployment-issuer-service.yaml#L38
Service Account Tokens are automatically mounted even if not necessary
|
|
KICS scan:
charts/ssi-credential-issuer/templates/cronjob-expiry-app.yaml#L35
Service Account Tokens are automatically mounted even if not necessary
|
|
KICS scan:
.github/workflows/trivy-dev.yml#L165
Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps mitigate the risk of a bad actor adding a backdoor to the action's repository, as they would need to generate a SHA-1 collision for a valid Git object payload. When selecting a SHA, you should verify it is from the action's repository and not a repository fork.
|
Loading