Skip to content

Plumber action: verify the caller's workflow lockfile with gh actions-lock --verify (on by default) #590

Description

@Exypte

Is your feature request related to a problem? Please describe.

Plumber reads .github/workflows/actions.lock and counts locked refs as pinned (#542), but it trusts what the lockfile says. It doesn't check that a locked commit actually belongs to the action repository at that ref, or that owner_id / repo_id still match. The github/actions-lockfile parser leaves that to the caller: Parse "does not verify pin integrity or that actions exist on GitHub; those checks belong to the caller".

gh actions-lock --verify does those checks. Its README describes it as "the same checks as a fix run", which "checks provenance before merge". We already run it in this repository's CI (.github/workflows/verify-lockfile.yml, #568). A repository that runs the Plumber action would otherwise have to set up a separate workflow to get this check.

Describe the solution you'd like

Add a step to action.yml that runs gh actions-lock --verify on the checked-out repository. It is on by default: the goal is to get users of the action onto workflow lockfiles.

  • New input verify-lockfile, default true. verify-lockfile: false opts out.
  • New input actions-lock-version with a pinned gh-actions-lock release as the default (currently 0.4.1). The extension is installed with gh extension install github/gh-actions-lock --pin <version>, as in verify-lockfile.yml.
  • A repository without .github/workflows/actions.lock gets a warning and the job continues. The warning explains how to create one (gh extension install github/gh-actions-lock && gh actions-lock) and how to opt out.
  • A verification failure fails the job.
  • soft-fail doesn't mask a verification failure (the same rule as exit 3). The job summary gets a line with the result. SARIF and artifacts are still uploaded.
  • With project set (remote scan, no checkout), there are no local files to verify. The step is skipped with a warning.
  • The step uses the github-token input as GH_TOKEN, like the install step does for gh attestation verify.

Opting out:

- uses: getplumber/plumber@vX
  with:
    verify-lockfile: false

Implementation Hints

  • This belongs in the composite action, not in plumber analyze, since analysis runs no external binaries (Remove gitleaks integration completely #310). The action already shells out to gh for gh attestation verify.
  • README and action docs: document the two inputs and say that --verify needs network access to the action repositories.
  • Test on the lock-file-consumer lab repository: a valid lockfile passes, a tampered commit fails, a missing lockfile warns and the job continues, verify-lockfile: false skips the step, and project is skipped with a warning.

Why It's Valuable

With this on by default, the Plumber action checks, in the same job, that the repository's locked action commits come from the repositories they claim to come from, instead of trusting the lockfile as written. Users get the provenance check without maintaining a separate verify workflow, and repositories without a lockfile get a warning that tells them how to adopt one.

References

Activity

  1. added theissue type on Nov 3, 2026
  2. thomasboni commented on Nov 3, 2026

    @thomasboni
    Contributor

    @Exypte seems good !

    One question: why do we disable verify-lockfile by default ? If a lock file is present, do we have any reason to not enable it ?

  3. self-assigned this
    on Nov 4, 2026
  4. Exypte commented on Nov 4, 2026

    @Exypte
    ContributorAuthor

    I'm working on this one, a fix is on the way.

  5. Exypte commented on Nov 4, 2026

    @Exypte
    ContributorAuthor

    @thomasboni Agreed, no good reason. It'll be on by default, and a repository without .github/workflows/actions.lock fails the job too: the goal is to get users onto workflow lockfiles. verify-lockfile: false opts out. I'll update the issue description.

  6. changed the title [-]Plumber action: opt-in `gh actions-lock --verify` step for the caller's workflow lockfile[/-] [+]Plumber action: verify the caller's workflow lockfile with `gh actions-lock --verify` (on by default)[/+] on Nov 4, 2026
  7. Exypte commented on Nov 5, 2026

    @Exypte
    ContributorAuthor

    @thomasboni Change from my last comment: a repository without .github/workflows/actions.lock now gets a warning and the job continues. A lockfile that doesn't verify still fails the job. verify-lockfile stays on by default, and I've updated the issue description.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions