chore: harden supply chain — hashes, SHA pins, weekly audit#63
Merged
datasciencemonkey merged 4 commits intomainfrom Mar 12, 2026
Merged
chore: harden supply chain — hashes, SHA pins, weekly audit#63datasciencemonkey merged 4 commits intomainfrom
datasciencemonkey merged 4 commits intomainfrom
Conversation
- Regenerate requirements.lock with --generate-hashes (3,057 SHA-256 entries) - Pin all GitHub Actions to immutable commit SHAs (checkout, setup-python, action-gh-release) - Pin pip-audit and uv to exact versions in CI - Add weekly cron schedule to dependency-audit workflow - Add npm package version check step to CI - Add pyproject.toml to audit trigger paths - Update lockfile freshness check to use --generate-hashes - Change Gemini CLI fallback from @nightly to @latest - Add dependabot.yml for automated weekly dependency updates Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
pip-audit auto-enables --require-hashes when it detects hashes in the lockfile, but sqlalchemy's conditional dependency (greenlet) isn't in the lockfile (platform-conditional). --no-deps tells pip-audit to audit only the explicitly listed packages, which is correct since the lockfile already contains all transitive deps. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
pip-audit's pip backend auto-enables --require-hashes when it sees hash entries, then fails on sqlalchemy's platform-conditional greenlet dep (present on x86_64 CI runners but absent from lockfile compiled on aarch64). Fix: strip --hash lines before auditing. The hashes are verified at install time via pip --require-hashes, not at audit time. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Addresses the two HIGH and three MEDIUM supply chain findings from the CoDA security report (supply chain score: 52/100).
Changes
--generate-hashespip-audit==2.9.0,uv==0.7.12pinned in workflow@latest(more stable, more audited)dependency-audit.ymlruns Monday 6am UTCpyproject.tomlchanges now trigger auditFiles
requirements.lock— regenerated with--generate-hashes.github/workflows/dependency-audit.yml— SHA pins, tool pins, npm audit, cron.github/workflows/release.yml— SHA pinssetup_gemini.py—@nightly→@latest.github/dependabot.yml— newTest plan
uv run pytest tests/ -v)# vXcomments🤖 Generated with Claude Code