Contract Security Analysis #654
security-analysis.yml
on: schedule
Shared
/
Backstage
9s
Matrix: Shared / Static Analysis
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 (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 (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 (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-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 / Backstage
The following actions uses node12 which is deprecated and will be forced to run on node16: aurora-is-near/github-helpers@main. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Shared / Backstage
The following actions uses Node.js version which is deprecated and will be forced to run on node20: aurora-is-near/github-helpers@main. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
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
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/
|