Skip to content

chore(workflows): move the five image pins to what 976ef61's build published - #104

Merged
garymike merged 1 commit into
mainfrom
chore/move-pins-976ef61
Nov 9, 2026
Merged

garymike merged 1 commit into
mainfrom
chore/move-pins-976ef61

Conversation

@garymike

@garymike garymike commented Nov 9, 2026

Copy link
Copy Markdown
Owner

The follow-up half of #103, and it covers #102 as well: both landed toolbox changes without moving a pin, so callers have been resolving images built before the nine-tool bump. For skill-audit-toolbox that gap was load-bearing, because #103's docs assert v2.13.4 numbers while the pinned image still carried v2.13.2.

Permitted, not forced

check-image-pins.py reported all 5 of 5 behind before the move, which is the state the mover's guard requires, so no --force was needed.

workflow image inputs then inputs now
gha-security.yml gha-toolbox 5c137c684483 f6a4a72e874a
iac-security.yml iac-toolbox f24b2cabd9b1 4a28bbf3e20f
sast.yml sast-toolbox de509bd1ace1 547b6bc2feaf
security-scan.yml security-toolbox-base 2aed68cf9f33 b4802091e180
skill-audit.yml skill-audit-toolbox b011e83c21f6 a36fc4fa94cf

Each digest was resolved from the per-commit sha-976ef61d7b38 tag rather than latest, and its build-inputs label read back out of the registry and compared with the fingerprint this repo computes now. All five matched before anything was written. check-image-pins.py now reports all five current.

Verified against the pinned digest, not a local build

This is the pin #103's claims rest on, so the proof ran against the image a caller will actually resolve:

ghcr.io/.../skill-audit-toolbox@sha256:be7c2732246a...
  SkillSpector v2.13.4, semgrep 1.184.0
  gate-proof.sh: 16 of 16

  FIXTURE                  SCORE     SKILLSPECTOR
  gecko-demo               64/100    exit 1, BLOCKS
  gecko-hook-demo          76/100    exit 1, BLOCKS
  config-injection-demo    100/100   exit 1, BLOCKS
  sibling-config-demo      51/100    exit 1, BLOCKS
  memory-poisoning-demo    27/100    exit 0, does NOT block

The 27/100 in README.md and docs/ is now what a caller resolving this pin gets.

…blished

The follow-up half of #103, and it covers #102 as well: both landed toolbox changes without
moving a pin, so callers have been resolving images built before the nine-tool bump. For
skill-audit-toolbox that gap was load-bearing, because #103's docs assert v2.13.4 numbers while
the pinned image still carried v2.13.2.

Permitted rather than forced. check-image-pins.py reported all 5 of 5 behind before the move,
which is the state the mover's guard requires, so no --force was needed:

    gha-security.yml      inputs 5c137c684483 -> f6a4a72e874a
    iac-security.yml      inputs f24b2cabd9b1 -> 4a28bbf3e20f
    sast.yml              inputs de509bd1ace1 -> 547b6bc2feaf
    security-scan.yml     inputs 2aed68cf9f33 -> b4802091e180
    skill-audit.yml       inputs b011e83c21f6 -> a36fc4fa94cf

Verified the usual way: each digest resolved from the per-commit sha-976ef61d7b38 tag rather than
latest, and its build-inputs label read back out of the registry and compared with the fingerprint
this repo computes now. All five matched before anything was written. check-image-pins.py now
reports all five current.

Verified one step further, because this is the pin #103's claims rest on. Pulled the
skill-audit-toolbox digest callers will now resolve and ran the proof against it, not against a
locally built image:

    SkillSpector v2.13.4, semgrep 1.184.0
    gate-proof.sh: 16 of 16

    gecko-demo               64/100    exit 1, BLOCKS
    gecko-hook-demo          76/100    exit 1, BLOCKS
    config-injection-demo    100/100   exit 1, BLOCKS
    sibling-config-demo      51/100    exit 1, BLOCKS
    memory-poisoning-demo    27/100    exit 0, does NOT block

The 27/100 in README.md and docs/ is now what a caller resolving this pin actually gets.
@garymike
garymike merged commit c6d0e21 into main Nov 9, 2026
9 checks passed
@garymike
garymike deleted the chore/move-pins-976ef61 branch November 9, 2026 18:33
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