Skip to content

chore(toolbox): bump checkov 3.4.0 -> 3.4.2 (tool-bump 2026-11-02) - #102

Merged
garymike merged 1 commit into
mainfrom
automated/tool-bumps
Nov 5, 2026
Merged

garymike merged 1 commit into
mainfrom
automated/tool-bumps

Conversation

@garymike

@garymike garymike commented Nov 3, 2026

Copy link
Copy Markdown
Owner

Opens the automated/tool-bumps branch that tool-bump.yml pushed on 2026-11-02 (be610a6, server-signed), so the normal PR checks run on it.

Bumped

Tool From To Files
checkov 3.4.0 3.4.2 toolbox/tools.lock, toolbox/iac/Dockerfile

Every image was built from these pins before the branch was written (see the Tool bump run from 2026-11-02 13:13 UTC).

Still outstanding after this merges

The Tool drift run at 17:44 UTC the same day reported three pins behind upstream that this branch does not move:

  • checkov 3.4.3 was published after the bump ran (this PR takes it to 3.4.2).
  • syft 1.55.0 → 1.56.0.
  • skillspector 2.13.2 → 2.13.3, which the drift job says needs SKILLSPECTOR_REF moved together with tools.lock and the fixtures re-measured.

So the drift gate stays red after this merge until those three move. After merging, Build toolbox images publishes new digests and the five reusable-workflow image pins need moving to them (scripts/move-image-pins.py), the same follow-up as #97 and #101.

Opened by the weekly GitHub security audit (2026-11-02).

Applied by tool-bump.yml and validated by building every image
from these pins before the branch was written.

### Bumped

| Tool | From | To | Files |
|---|---|---|---|
| checkov | `3.4.0` | `3.4.2` | toolbox/tools.lock x1, toolbox/iac/Dockerfile |
@garymike
garymike merged commit 8875876 into main Nov 5, 2026
9 checks passed
@garymike
garymike deleted the automated/tool-bumps branch November 5, 2026 02:08
garymike added a commit that referenced this pull request Nov 9, 2026
…blished (#104)

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.
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