Skip to content

[plan] Pin install-gh-aw.sh curl script URL to commit SHA in workflows #19008

Closed as not planned

Description

@github-actions

Objective

Pin the install-gh-aw.sh script URL to a specific commit SHA in copilot-setup-steps and daily-copilot-token-report workflows to eliminate supply chain risk, as identified by poutine in discussion #19004.

Context

Both workflows execute:

curl -fsSL https://raw.githubusercontent.com/github/gh-aw/refs/heads/main/install-gh-aw.sh | bash

This fetches and executes the latest version of the script from refs/heads/main without integrity verification. If the branch is compromised or the file is modified maliciously, the attack executes silently in the runner. Pinning to a specific commit SHA prevents this.

Source: Static Analysis Report - 2026-03-01, poutine unverified_script_exec finding.

Approach

  1. Get the current HEAD commit SHA of the main branch:
    git rev-parse HEAD
  2. Open .github/workflows/copilot-setup-steps.yml and update the curl URL to use the commit SHA:
    # Before:
    curl -fsSL https://raw.githubusercontent.com/github/gh-aw/refs/heads/main/install-gh-aw.sh | bash
    # After:
    curl -fsSL https://raw.githubusercontent.com/github/gh-aw/(COMMIT_SHA)/install-gh-aw.sh | bash
  3. Open .github/workflows/daily-copilot-token-report.md and apply the same fix to the install script URL
  4. Run make recompile to regenerate lock files
  5. Add a comment in the workflow near the URL indicating the SHA should be updated on new releases

Files to Modify

  • .github/workflows/copilot-setup-steps.yml — pin curl URL to commit SHA
  • .github/workflows/daily-copilot-token-report.md — pin curl URL to commit SHA
  • .github/workflows/daily-copilot-token-report.lock.yml — regenerated via make recompile

Acceptance Criteria

  • Both workflows use a pinned commit SHA instead of refs/heads/main for the install script URL
  • make agent-finish passes
  • Poutine unverified_script_exec no longer fires for the pinned URLs

Generated by Plan Command for issue #discussion #19004

  • expires on Mar 3, 2026, 6:38 AM UTC
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions