Skip to content

Security Analysis

Security Analysis #43

Triggered via schedule January 10, 2025 00:28
Status Success
Total duration 1m 39s
Artifacts

security-analysis.yml

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

Annotations

5 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 (sputnikvm-runtime, ethereum, runtime, 1, ., 1.18, true, --filter-paths "node_mod...
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 (sputnikvm-gasometer, ethereum, gasometer, 1, ., 1.18, true, --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 (sputnikvm-evm, ethereum, 1, ., 1.18, true, --filter-paths "node_modules|testing|...
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 (sputnikvm-core, ethereum, core, 1, ., 1.18, true, --filter-paths "node_modules|t...
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