Pin and verify Docker and Compose binary downloads

Open
#225 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
56/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
docker

Research direction

Start by locating the image build definitions and the existing image revision update contract; the payload does not name specific files or checks. Identify where Docker and Compose binaries are selected and installed, then inspect the November 17 audit report for validation constraints. Done means supported architectures use explicit reviewed versions, verify integrity before installation, fail on mismatches, and have documented update steps plus a verification check.

Written by the indexing model from the issue text.

Description

enhancement

What to build

Make image builds fetch explicitly versioned Docker/Compose binaries and verify the downloaded bytes against reviewed integrity metadata before use.

Context

Supply-chain hardening follow-up to #118. Existing workflow action pinning does not cover binary downloads during the image build.

This follows the November 17 source audit. Treat it as a hardening/validation task, not a confirmed exploit report. Detailed audit evidence and validation limitations remain in the local audit report; report any confirmed vulnerability privately under SECURITY.md.

Acceptance criteria

  • Replace mutable latest binary selection with explicit reviewed versions for each supported architecture.
  • Validate integrity before installation and fail the build on a mismatch.
  • Document how versions and expected digests are updated; add a verification check for supported architectures.
  • Raise the image revision when implementation changes image behavior, following the existing update contract.
  • Internal build change; wiki exempt unless installation or update instructions change.

Blocked by

None (can start independently). Coordinate with related issues without expanding their scope.

Dominant language
TypeScript
Stars
1
Forks
0
Avg merge
13h 12m
Merged PRs (30d)
57

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Isopod-Project/Isopod

All issues in Isopod-Project/Isopod

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.