unpinned action reference: action is not pinned to a hash (required by blanket policy)

unpinned action reference: action is not pinned to a hash (required by blanket policy)

unpinned action reference: action is not pinned to a hash (required by blanket policy)

unpinned action reference: action is not pinned to a hash (required by blanket policy)

code injection via template expansion: may expand into attacker-controllable code

code injection via template expansion: may expand into attacker-controllable code

code injection via template expansion: may expand into attacker-controllable code

code injection via template expansion: may expand into attacker-controllable code

code injection via template expansion: may expand into attacker-controllable code

Found 12 findings for mandatory checks that must always succeed.

workflow.yml:103: unpinned action reference: action is not pinned to a hash (required by blanket policy)

workflow.yml:98: unpinned action reference: action is not pinned to a hash (required by blanket policy)

workflow.yml:95: unpinned action reference: action is not pinned to a hash (required by blanket policy)

workflow.yml:65: unpinned action reference: action is not pinned to a hash (required by blanket policy)

workflow.yml:61: unpinned action reference: action is not pinned to a hash (required by blanket policy)

workflow.yml:30: unpinned action reference: action is not pinned to a hash (required by blanket policy)

workflow.yml:26: unpinned action reference: action is not pinned to a hash (required by blanket policy)

workflow.yml:93: code injection via template expansion: may expand into attacker-controllable code

workflow.yml:59: code injection via template expansion: may expand into attacker-controllable code

workflow.yml:24: code injection via template expansion: may expand into attacker-controllable code

On November 2, 2026, GitHub will restrict `pull_request_target` on public repositories by default. To continue allowing the event trigger, configure an Actions policy. Learn more: https://gh.io/securely-using-pull_request_target#default-policy-for-pull_request_target

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: google-github-actions/auth@c200f3691d83b41bf9bbd8638997a462592937ed. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: google-github-actions/auth@c200f3691d83b41bf9bbd8638997a462592937ed. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

workflow.yml:87: overly broad permissions: default permissions used due to no permissions: block

workflow.yml:53: overly broad permissions: default permissions used due to no permissions: block

workflow.yml:18: overly broad permissions: default permissions used due to no permissions: block

workflow.yml:1: overly broad permissions: default permissions used due to no permissions: block

"The ubuntu-latest label will migrate to Ubuntu 26 beginning October 19, 2026. For more information, see https://github.com/actions/runner-images/issues/14748"

"The ubuntu-latest label will migrate to Ubuntu 26 beginning October 19, 2026. For more information, see https://github.com/actions/runner-images/issues/14748"

"The ubuntu-latest label will migrate to Ubuntu 26 beginning October 19, 2026. For more information, see https://github.com/actions/runner-images/issues/14748"

"The ubuntu-latest label will migrate to Ubuntu 26 beginning October 19, 2026. For more information, see https://github.com/actions/runner-images/issues/14748"