You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Pin the remaining unpinned third-party dependencies that Scorecard flags: the golang:1.24-alpine builder image in both API Dockerfiles, and the unhashed pip install PyYAML==6.0.2 in ci.yml. Also add a CI test so new unpinned dependencies can't creep back in.
First-party combsmith/.github* reusable-workflow channel refs (@<agent>/vN-stable) are intentionally left as they are. They fall under the org "Release channel tags & the mutable-ref exception" and the stub headers say they must not change. Scorecard will keep counting them, so this change may not reach 10/10 alone.
Implementation Checklist
apps/api/Dockerfile, apps/api/Dockerfile.worker: FROM golang:1.24-alpine@sha256:<digest>
tests/scripts/requirements.txt (new): PyYAML==6.0.2 with --hash=sha256: entries
.github/workflows/ci.yml: install PyYAML with pip install --require-hashes -r tests/scripts/requirements.txt, and run the new guard test
.github/dependabot.yml: add docker (/apps/api) and pip (/tests/scripts) ecosystems so digests and hashes keep getting refreshed
Tests to Write
tests/scripts/pinned-dependencies.test.sh: every Dockerfile FROM is digest-pinned, every workflow pip install uses --require-hashes, and every requirements entry has a --hash
Test Command
bash tests/scripts/pinned-dependencies.test.sh (plus the existing shell tests and bash .dev-lead/scripts/dev-lead-lint.sh)
The implementation for issue #395 is durable: commits are pushed and a pull request is open. This record is backed by verifiable artifacts you can confirm in one click.
Review happens on the PR. Acceptance criteria and test results are evidenced by the PR's diff and CI checks — not asserted here. If a later stage fails, this claim is retracted in place.
Activity
don-petry commentedon Jul 20, 2026
Weekly update: Score is now 5/10. Finding: dependency not pinned by hash detected -- score normalized to 5
don-petry commentedon Jul 27, 2026
Weekly update: Score is now 5/10. Finding: dependency not pinned by hash detected -- score normalized to 5
don-petry commentedon Aug 3, 2026
Weekly update: Score is now 5/10. Finding: dependency not pinned by hash detected -- score normalized to 5
don-petry commentedon Aug 10, 2026
Weekly update: Score is now 5/10. Finding: dependency not pinned by hash detected -- score normalized to 5
don-petry commentedon Aug 17, 2026
Weekly update: Score is now 5/10. Finding: dependency not pinned by hash detected -- score normalized to 5
don-petry commentedon Aug 24, 2026
Weekly update: Score is now 5/10. Finding: dependency not pinned by hash detected -- score normalized to 5
don-petry commentedon Aug 31, 2026
Weekly update: Score is now 5/10. Finding: dependency not pinned by hash detected -- score normalized to 5
don-petry commentedon Sep 7, 2026
Weekly update: Score is now 5/10. Finding: dependency not pinned by hash detected -- score normalized to 5
don-petry commentedon Sep 14, 2026
Weekly update: Score is now 5/10. Finding: dependency not pinned by hash detected -- score normalized to 5
don-petry commentedon Sep 21, 2026
Weekly update: Score is now 5/10. Finding: dependency not pinned by hash detected -- score normalized to 5
don-petry commentedon Sep 28, 2026
Weekly update: Score is now 5/10. Finding: dependency not pinned by hash detected -- score normalized to 5
don-petry commentedon Oct 5, 2026
Weekly update: Score is now 5/10. Finding: dependency not pinned by hash detected -- score normalized to 5
don-petry commentedon Oct 12, 2026
Weekly update: Score is now 5/10. Finding: dependency not pinned by hash detected -- score normalized to 5
don-petry commentedon Oct 19, 2026
Weekly update: Score is now 5/10. Finding: dependency not pinned by hash detected -- score normalized to 5
don-petry commentedon Oct 20, 2026
Weekly update: Score is now 5/10. Finding: dependency not pinned by hash detected -- score normalized to 5
don-petry commentedon Oct 26, 2026
Weekly update: Score is now 5/10. Finding: dependency not pinned by hash detected -- score normalized to 5
don-petry commentedon Nov 2, 2026
Weekly update: Score is now 5/10. Finding: dependency not pinned by hash detected -- score normalized to 5
don-petry commentedon Nov 9, 2026
Weekly update: Score is now 5/10. Finding: dependency not pinned by hash detected -- score normalized to 5
don-petry commentedon Nov 10, 2026
Dev-Lead Implementation Plan
Issue: #395 — Scorecard: Pinned-Dependencies (5/10)
Scope
Pin the remaining unpinned third-party dependencies that Scorecard flags: the
golang:1.24-alpinebuilder image in both API Dockerfiles, and the unhashedpip install PyYAML==6.0.2inci.yml. Also add a CI test so new unpinned dependencies can't creep back in.First-party
combsmith/.github*reusable-workflow channel refs (@<agent>/vN-stable) are intentionally left as they are. They fall under the org "Release channel tags & the mutable-ref exception" and the stub headers say they must not change. Scorecard will keep counting them, so this change may not reach 10/10 alone.Implementation Checklist
apps/api/Dockerfile,apps/api/Dockerfile.worker:FROM golang:1.24-alpine@sha256:<digest>tests/scripts/requirements.txt(new):PyYAML==6.0.2with--hash=sha256:entries.github/workflows/ci.yml: install PyYAML withpip install --require-hashes -r tests/scripts/requirements.txt, and run the new guard test.github/dependabot.yml: adddocker(/apps/api) andpip(/tests/scripts) ecosystems so digests and hashes keep getting refreshedTests to Write
tests/scripts/pinned-dependencies.test.sh: every DockerfileFROMis digest-pinned, every workflowpip installuses--require-hashes, and every requirements entry has a--hashTest Command
bash tests/scripts/pinned-dependencies.test.sh(plus the existing shell tests andbash .dev-lead/scripts/dev-lead-lint.sh)don-petry commentedon Nov 10, 2026
Dev-Lead: Implementation Complete — PR #646
The implementation for issue #395 is durable: commits are pushed and a pull request is open. This record is backed by verifiable artifacts you can confirm in one click.
43626502efc9af494b637b21675b4f83eb5712bcmain: 6 file(s), +139/-3 linesReview happens on the PR. Acceptance criteria and test results are evidenced by the PR's diff and CI checks — not asserted here. If a later stage fails, this claim is retracted in place.
fix(bot): remove out-of-scope .coderabbit.yaml changes
don-petry commentedon Nov 16, 2026
Weekly update: Score is now 5/10. Finding: dependency not pinned by hash detected -- score normalized to 5