Skip to content

chore: add audit report #141

chore: add audit report

chore: add audit report #141

Triggered via push May 18, 2026 12:30
Status Failure
Total duration 5m 4s
Artifacts 1

build.yaml

on: push
Matrix: stack
Matrix: validate
Fit to window
Zoom out
Zoom in

Annotations

9 errors and 14 warnings
validate (op-batcher, ghcr.io, rss3-network/optimism)
get sts token failed with OIDC: {"RequestId":"BFBAE0B1-914C-50CB-881E-D941EB5D6D2C","HostId":"sts.aliyuncs.com","Code":"AuthenticationFail.OIDCToken.PublicKeyFingerprintMismatch","Message":"The https fingerprint of this discovery is invalid.","Recommend":"https://api.aliyun.com/troubleshoot?q=AuthenticationFail.OIDCToken.PublicKeyFingerprintMismatch&product=Sts&requestId=BFBAE0B1-914C-50CB-881E-D941EB5D6D2C"}
validate (op-batcher, docker.io, rss3)
get sts token failed with OIDC: {"RequestId":"69A0448C-1ACD-589E-B0B0-45CB6FC540E8","HostId":"sts.aliyuncs.com","Code":"AuthenticationFail.OIDCToken.PublicKeyFingerprintMismatch","Message":"The https fingerprint of this discovery is invalid.","Recommend":"https://api.aliyun.com/troubleshoot?q=AuthenticationFail.OIDCToken.PublicKeyFingerprintMismatch&product=Sts&requestId=69A0448C-1ACD-589E-B0B0-45CB6FC540E8"}
validate (op-batcher, container-registry.us-east-1.cr.aliyuncs.com, rss3)
get sts token failed with OIDC: {"RequestId":"B786BAFD-22F8-5C90-8027-57E9189D1FC6","HostId":"sts.aliyuncs.com","Code":"AuthenticationFail.OIDCToken.PublicKeyFingerprintMismatch","Message":"The https fingerprint of this discovery is invalid.","Recommend":"https://api.aliyun.com/troubleshoot?q=AuthenticationFail.OIDCToken.PublicKeyFingerprintMismatch&product=Sts&requestId=B786BAFD-22F8-5C90-8027-57E9189D1FC6"}
validate (op-node, ghcr.io, rss3-network/optimism)
get sts token failed with OIDC: {"RequestId":"4C239F02-38B1-5100-9903-F96F1C94CDB5","HostId":"sts.aliyuncs.com","Code":"AuthenticationFail.OIDCToken.PublicKeyFingerprintMismatch","Message":"The https fingerprint of this discovery is invalid.","Recommend":"https://api.aliyun.com/troubleshoot?q=AuthenticationFail.OIDCToken.PublicKeyFingerprintMismatch&product=Sts&requestId=4C239F02-38B1-5100-9903-F96F1C94CDB5"}
validate (op-node, docker.io, rss3)
get sts token failed with OIDC: {"RequestId":"75116BF3-5A95-5FC8-BE7D-0B77775DFCC4","HostId":"sts.aliyuncs.com","Code":"AuthenticationFail.OIDCToken.PublicKeyFingerprintMismatch","Message":"The https fingerprint of this discovery is invalid.","Recommend":"https://api.aliyun.com/troubleshoot?q=AuthenticationFail.OIDCToken.PublicKeyFingerprintMismatch&product=Sts&requestId=75116BF3-5A95-5FC8-BE7D-0B77775DFCC4"}
validate (op-node, container-registry.us-east-1.cr.aliyuncs.com, rss3)
get sts token failed with OIDC: {"RequestId":"17C7BC3C-C39B-58C0-A85D-2CBA890DEBEA","HostId":"sts.aliyuncs.com","Code":"AuthenticationFail.OIDCToken.PublicKeyFingerprintMismatch","Message":"The https fingerprint of this discovery is invalid.","Recommend":"https://api.aliyun.com/troubleshoot?q=AuthenticationFail.OIDCToken.PublicKeyFingerprintMismatch&product=Sts&requestId=17C7BC3C-C39B-58C0-A85D-2CBA890DEBEA"}
validate (op-proposer, container-registry.us-east-1.cr.aliyuncs.com, rss3)
get sts token failed with OIDC: {"RequestId":"796803DB-F780-5AEB-A3DC-7E5B2750BF4A","HostId":"sts.aliyuncs.com","Code":"AuthenticationFail.OIDCToken.PublicKeyFingerprintMismatch","Message":"The https fingerprint of this discovery is invalid.","Recommend":"https://api.aliyun.com/troubleshoot?q=AuthenticationFail.OIDCToken.PublicKeyFingerprintMismatch&product=Sts&requestId=796803DB-F780-5AEB-A3DC-7E5B2750BF4A"}
validate (op-proposer, ghcr.io, rss3-network/optimism)
get sts token failed with OIDC: {"RequestId":"879169CE-C47D-5E89-8B3E-EE9F6AC20098","HostId":"sts.aliyuncs.com","Code":"AuthenticationFail.OIDCToken.PublicKeyFingerprintMismatch","Message":"The https fingerprint of this discovery is invalid.","Recommend":"https://api.aliyun.com/troubleshoot?q=AuthenticationFail.OIDCToken.PublicKeyFingerprintMismatch&product=Sts&requestId=879169CE-C47D-5E89-8B3E-EE9F6AC20098"}
validate (op-proposer, docker.io, rss3)
get sts token failed with OIDC: {"RequestId":"A9DCA350-0E7F-578D-B449-CDFFB47D5890","HostId":"sts.aliyuncs.com","Code":"AuthenticationFail.OIDCToken.PublicKeyFingerprintMismatch","Message":"The https fingerprint of this discovery is invalid.","Recommend":"https://api.aliyun.com/troubleshoot?q=AuthenticationFail.OIDCToken.PublicKeyFingerprintMismatch&product=Sts&requestId=A9DCA350-0E7F-578D-B449-CDFFB47D5890"}
prepare
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/github-script@v7. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
stack (op-stack-go)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/bake-action@v5, docker/login-action@v3, docker/setup-qemu-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Variables should be defined before their use: ops/docker/op-stack-go/Dockerfile#L26
UndefinedVar: Usage of undefined variable '$LD_LIBRARY_PATH' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/
The 'as' keyword should match the case of the 'from' keyword: ops/docker/op-stack-go/Dockerfile#L7
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
The 'as' keyword should match the case of the 'from' keyword: ops/docker/op-stack-go/Dockerfile#L2
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
validate (op-batcher, ghcr.io, rss3-network/optimism)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, aliyun/configure-aliyun-credentials-action@v1, docker/setup-qemu-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
validate (op-batcher, docker.io, rss3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, aliyun/configure-aliyun-credentials-action@v1, docker/setup-qemu-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
validate (op-batcher, container-registry.us-east-1.cr.aliyuncs.com, rss3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, aliyun/configure-aliyun-credentials-action@v1, docker/setup-qemu-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
validate (op-node, ghcr.io, rss3-network/optimism)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, aliyun/configure-aliyun-credentials-action@v1, docker/setup-qemu-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
validate (op-node, docker.io, rss3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, aliyun/configure-aliyun-credentials-action@v1, docker/setup-qemu-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
validate (op-node, container-registry.us-east-1.cr.aliyuncs.com, rss3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, aliyun/configure-aliyun-credentials-action@v1, docker/setup-qemu-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
validate (op-proposer, container-registry.us-east-1.cr.aliyuncs.com, rss3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, aliyun/configure-aliyun-credentials-action@v1, docker/setup-qemu-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
validate (op-proposer, ghcr.io, rss3-network/optimism)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, aliyun/configure-aliyun-credentials-action@v1, docker/setup-qemu-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
validate (op-proposer, docker.io, rss3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, aliyun/configure-aliyun-credentials-action@v1, docker/setup-qemu-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Artifacts

Produced during runtime
Name Size Digest
RSS3-Network~optimism~PKVBDE.dockerbuild Expired
89.3 KB
sha256:10f6a545f46352860ca5c0112cb9960b7273ccc94725b02a35c6455045354437