Skip to content
Contract Security Analysis

Improve the Omni api integration #749

Sign in to view logs

Improve the Omni api integration

Improve the Omni api integration #749

Triggered via pull request February 4, 2025 12:29
@karim-enkarim-en
synchronize #253
omni_token-improvments
Status Success
Total duration 2m 30s
Artifacts –

security-analysis.yml

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

Annotations

16 errors and 7 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 (erc20-locker, contract, ethereum, erc20-connector, 1, erc20-connector, 1.18, tru...
Process completed with exit code 1.
Shared / Static Analysis (erc20-locker, contract, ethereum, erc20-connector, 1, erc20-connector, 1.18, tru...
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 (silo-to-silo, contract, aurora, silo-to-silo, 1, silo-to-silo, 1.18, true, --fil...
Process completed with exit code 1.
Shared / Static Analysis (silo-to-silo, contract, aurora, silo-to-silo, 1, silo-to-silo, 1.18, true, --fil...
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 (bridge-token-factory-on-near, contract, near, bridge-token-factory, 1, ., 1.18, ...
Process completed with exit code 101.
Shared / Static Analysis (bridge-token-factory-on-near, contract, near, bridge-token-factory, 1, ., 1.18, ...
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 (bridge-token-factory-on-near, contract, near, bridge-token-factory, 1, ., 1.18, ...
Process completed with exit code 101.
Shared / Static Analysis (bridge-token-on-near, contract, near, bridge-token, 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 / Static Analysis (bridge-token-on-near, contract, near, bridge-token, 1, ., 1.18, false, --filter-...
Process completed with exit code 101.
Shared / Static Analysis (erc20-bridge-token, contract, ethereum, erc20-bridge-token, 1, erc20-bridge-toke...
Process completed with exit code 1.
Shared / Static Analysis (erc20-bridge-token, contract, ethereum, erc20-bridge-token, 1, erc20-bridge-toke...
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 (bridge-near-token-locker, contract, near, token-locker, 1, ., 1.18, false, --fil...
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 (bridge-near-token-locker, contract, near, token-locker, 1, ., 1.18, false, --fil...
Process completed with exit code 101.
Shared / Static Analysis (bridge-common, contract, near, bridge-common, 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 (bridge-common, contract, near, bridge-common, 1, ., 1.18, false, --filter-paths ...
Process completed with exit code 101.
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
unable to detect go version
Shared / Backstage
unable to detect go version
Shared / Backstage
unable to detect go version