Skip to content

fix: extracting docker image name for scan correctly #3264

fix: extracting docker image name for scan correctly

fix: extracting docker image name for scan correctly #3264

Triggered via pull request November 7, 2024 16:37
Status Success
Total duration 8m 4s
Artifacts 2

on-pr.yml

on: pull_request
Execute doc examples
4m 0s
Execute doc examples
test-apps  /  Install and test example apps
3m 26s
test-apps / Install and test example apps
rpc-proxy  /  ...  /  test
4m 30s
rpc-proxy / test / test
rpc-proxy  /  ...  /  docker
2m 20s
rpc-proxy / docker / docker
install-build  /  Build & Lint
3m 16s
install-build / Build & Lint
Matrix: unit-integration-test-browser / Build & Lint
Matrix: unit-integration-test / Build & Lint
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
install-build / Build & Lint: apps/sdk-vite-integration/src/const/index.tsx#L1
This rule can't verify that `export *` only exports components
install-build / Build & Lint: packages/rpc-proxy/src/utils/config-validator/config-validator.ts#L27
Found existsSync from package "fs" with non literal argument at index 0
install-build / Build & Lint: packages/rpc-proxy/src/utils/config-validator/config-validator.ts#L48
Found readFileSync from package "fs" with non literal argument at index 0
install-build / Build & Lint: packages/rpc-proxy/src/utils/config-validator/config-validator.ts#L75
Found readFileSync from package "fs" with non literal argument at index 0
install-build / Build & Lint: packages/rpc-proxy/src/utils/config-validator/config-validator.ts#L229
Found readFileSync from package "fs" with non literal argument at index 0

Artifacts

Produced during runtime
Name Size
coverage-results Expired
33.5 KB
vechain~vechain-sdk-js~9FRQI0.dockerbuild Expired
39.1 KB