Skip to content

Security Analysis

Security Analysis #40

Triggered via schedule January 11, 2025 00:27
Status Failure
Total duration 4m 1s
Artifacts

security-analysis.yml

on: schedule
Shared  /  Backstage
7s
Shared / Backstage
Matrix: Shared / Static Analysis
Fit to window
Zoom out
Zoom in

Annotations

8 errors and 9 warnings
Shared / Backstage
The ssh-private-key argument is empty. Maybe the secret has not been configured, or you are using a wrong secret name in your workflow file.
Shared / Static Analysis (btc-light-client-merkle-tools, near, merkle-tools, 1, ., 1.18, false, --filter-p...
The ssh-private-key argument is empty. Maybe the secret has not been configured, or you are using a wrong secret name in your workflow file.
Shared / Static Analysis (btc-light-client-btc-types, near, btc-types, 1, ., 1.18, false, --filter-paths "...
The ssh-private-key argument is empty. Maybe the secret has not been configured, or you are using a wrong secret name in your workflow file.
Shared / Static Analysis (btc-light-client-relayer, near, relayer, 1, ., 1.18, false, --filter-paths "node...
The ssh-private-key argument is empty. Maybe the secret has not been configured, or you are using a wrong secret name in your workflow file.
Shared / Static Analysis (btc-light-client-contract, contract, near, contract, 1, ., 1.18, false, --filter...
The ssh-private-key argument is empty. Maybe the secret has not been configured, or you are using a wrong secret name in your workflow file.
Shared / Backstage
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Shared / Backstage
unable to detect go version
Shared / Backstage
unable to detect go version
Shared / Backstage
unable to detect go version
Shared / Backstage
unable to detect go version