Skip to content

ci: fix high-severity zizmor findings - #208

Merged
Keerthi Gowda (keerthi-go) merged 1 commit into
mainfrom
fix/zizmor-security-findings
Jul 28, 2026
Merged

ci: fix high-severity zizmor findings#208
Keerthi Gowda (keerthi-go) merged 1 commit into
mainfrom
fix/zizmor-security-findings

Conversation

@keerthi-go

@keerthi-go Keerthi Gowda (keerthi-go) commented Jul 27, 2026

Copy link
Copy Markdown
Contributor

Summary

  • remediate repo-wide high-severity template-injection findings by routing template expressions through env variables
  • remove github-env high findings in push_to_repo by using step outputs instead of writing to GITHUB_ENV
  • add a targeted zizmor: ignore[unpinned-images] for the dynamic suite-based pkg-builder container image

Validation

  • ran zizmor --config /tmp/zizmor-policy.yml --min-severity high --persona regular .
  • result: no high-severity findings

Fix the repo-wide high-severity zizmor findings across actions and
workflows.

Move template expressions out of shell run blocks by routing values
through step env variables, replace GITHUB_ENV writes in push_to_repo
with step outputs, and add a scoped ignore for the dynamic suite-based
pkg-builder image reference.

Also fix remaining template-injection findings in abi_checker and in
the disabled installability validation step in
pkg-build-reusable-workflow.

Normalize touched step formatting so step-level env blocks are placed
before run blocks for consistency.

Signed-off-by: Keerthi Gowda <kbalehal@qti.qualcomm.com>

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

works

@keerthi-go
Keerthi Gowda (keerthi-go) merged commit 245876c into main Jul 28, 2026
20 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants