Skip to content

Lockfiles and pinning

Use the Vulnesis actions with GitHub Actions lockfiles and SHA pins, and how each action ref selects the CLI binary it installs.

Updated 05 Nov 2026Markdown

The Vulnesis actions work with GitHub’s workflow lockfile, .github/workflows/actions.lock.

gh extension install github/gh-actions-lock
gh actions-lock
gh actions-lock --verify

Refs such as Vulnesis/cli/sast/python@v4 narrow to the exact release, and nested paths lock like any other. The third-party actions the composites use are pinned by commit SHA and locked with them.

Local actions

Once a repository has a lock file, GitHub also enforces it on a local uses: ./my-action composite: every third-party action inside it must be locked, or the job fails with lockfile missing pin. Run the following to move local actions to $/ refs, which the lock covers:

gh actions-lock --migrate-local-actions

A $/ ref resolves to the commit of the workflow itself, not to whatever an earlier step checked out. A step that checks out another ref and then runs an action from it needs another approach, such as calling that ref’s script directly. actionlint 1.7.12 reports $/ as an invalid format, so lint a copy with the refs rewritten to ./.

Dependabot

Dependabot updates actions.lock in the same pull request as the action refs, so a bump passes lock verification. Group the bumps so one pull request carries them.

The exception is a repository with $/ local actions: Dependabot cannot read them, and an update under that directory fails with can't inspect self repository action. Relock those by hand with gh actions-lock.

In CI, verify with gh actions-lock --verify-local. The online check also reads each third-party action’s repository, and an organisation with an IP allow list refuses a workflow token.

What a lock freezes

A lock freezes an action’s commit. It does not freeze what that commit downloads, so each release tag names its own binary in action-lib/cli-release:

version input Installs
empty (the default) The release this action ref was cut from
v4.23.1 That release
v4 or latest Whatever is newest when the job runs. A lock cannot freeze this

So leave version empty on a locked or SHA-pinned workflow. The action, its scripts and the binary then all come from one release.

verify-provenance is on by default, so the action verifies the binary’s signed provenance and its SHA-256 checksum. Release assets sit outside the lock: this check is what binds them to the release.

How @v4 moves

@v4 moves to a release only after a canary installs that release through its own setup action and confirms the binary is the tag. It only moves forward, so a locked commit stays reachable from its tag.

Require lockfile

GitHub’s Require lockfile policy also blocks workflows with no uses: and callers of reusable workflows that are not onboarded. Reusable workflows are not pinned by a lock: refer to them by full SHA.

esc
↑ ↓ move↵ openSearches in your browser. A key like autonomy.max or a code like threshold_required jumps straight to it.