Skip to content

ci: add security workflow #1

ci: add security workflow

ci: add security workflow #1

Triggered via pull request November 29, 2024 12:13
Status Success
Total duration 1m 21s
Artifacts

security-analysis.yml

on: pull_request
Shared  /  Backstage
4s
Shared / Backstage
Matrix: Shared / Static Analysis
Fit to window
Zoom out
Zoom in

Annotations

5 errors and 5 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-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-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-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-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 / 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
Shared / Backstage
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/