Skip to content

ci: add scheduled security run (#72) #8

ci: add scheduled security run (#72)

ci: add scheduled security run (#72) #8

Triggered via push December 18, 2024 16:55
Status Success
Total duration 1m 43s
Artifacts
Shared  /  Backstage
6s
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-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 / 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 / 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