ACB-GEN-002: External code and dependencies are pinned immutably

FieldValue
Statusdraft
Severityhigh
Check typestatic
Applies toskill, instruction-file, mcp-server-declaration
Profilesstrict-general
Exceptionspermitted

Description

Every package, tool, container image or remote file that an artifact installs, runs or instructs the agent to install or run is pinned to an immutable reference: an exact version with an integrity digest, a content digest, or a full commit hash.

Rationale

Agent artifacts are executed long after review. A floating reference (latest, a branch, a version range, an unversioned package name) means the code that runs is not the code that was reviewed. MCP server declarations that launch unpinned packages through a package runner are a common case: every client start may fetch a different release.

Audit procedures

package-runners-pinned (pattern)

Invocations of package runners and installers specify an exact version. Version ranges, dist-tags and bare package names fail.

Illustrative failing indicators (non-exhaustive):

lockfile-or-hash (pattern)

Where an exact version is given, an integrity mechanism is also present: a lockfile with hashes bundled in the artifact, a --require-hashes style flag, or an explicit digest check.

images-by-digest (pattern)

Container image references include an @sha256: digest.

Illustrative failing indicators (non-exhaustive):

downloads-verified (pattern)

Every fetched URL (curl, wget, Invoke-WebRequest, language HTTP clients in scripts) is followed by a digest verification against a value in the artifact, or the URL itself contains a full 40 or 64 character commit hash.

Illustrative failing indicators (non-exhaustive):

Remediation

Pin every reference to an exact version and add an integrity check: bundle a hashed lockfile, pin images by digest, reference repository content by commit hash, and verify downloaded files with a pinned SHA-256 before use.

References