Skip to content

Potential fix for code scanning alert no. 13: Cache Poisoning via execution of untrusted code - #31

Merged
digreatbrian merged 1 commit into
mainfrom
alert-autofix-13
Jul 3, 2026
Merged

Potential fix for code scanning alert no. 13: Cache Poisoning via execution of untrusted code#31
digreatbrian merged 1 commit into
mainfrom
alert-autofix-13

Conversation

@digreatbrian

Copy link
Copy Markdown
Member

Potential fix for https://github.com/duckframework/duck/security/code-scanning/13

Best fix: do not run this PyPI publish workflow from workflow_run. Keep only trusted/manual/tag triggers so the workflow runs from explicitly trusted refs.

In .github/workflows/pypi-publish.yml:

  • Remove the workflow_run trigger block under on:.
  • Simplify checkout ref to avoid referencing github.event.workflow_run.head_sha; use only inputs.tag (manual) or github.ref (tag push).

This preserves intended functionality (publish by tag push or manual dispatch) while removing the untrusted trigger path.

Suggested fixes powered by Copilot Autofix. Review carefully before merging.

…cution of untrusted code

Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
@digreatbrian
digreatbrian marked this pull request as ready for review July 3, 2026 10:30
@digreatbrian
digreatbrian merged commit 50e5049 into main Jul 3, 2026
6 checks passed
@digreatbrian
digreatbrian deleted the alert-autofix-13 branch July 3, 2026 10:30
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.

1 participant