security: supply chain hardening#1
Merged
Merged
Conversation
…acks Pin all Actions steps to full commit SHAs, add StepSecurity Harden-Runner with egress audit, declare explicit least-privilege permissions (contents: read, id-token: none), switch to hash-locked dependency install (--require-hashes), add pip-audit and SBOM generation steps, and run scripts/check_workflows.py as a supply-chain guard on every CI run. Triggered by TanStack Mini Shai-Hulud attack (May 2026). See docs/SUPPLY_CHAIN_SECURITY_REFERENCE for full hardening rationale. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…+ SBOM tooling Add requirements.in, requirements.txt (73 sha256 entries), requirements-dev.in, and requirements-dev.txt (826 sha256 entries) generated with pip-compile --generate-hashes. Add pip-audit>=2.7 and cyclonedx-bom>=4.0 to dev deps so CI can audit for CVEs and generate a CycloneDX SBOM on every build. CI now installs exclusively via --require-hashes from the lockfile, never via live PyPI resolution. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Document 11 supply-chain invariants for every AI coding agent working on this repo: no pull_request_target with fork code, explicit workflow permissions, id-token: write only in release.yml, no cache in release jobs, SHA-pinned Actions, no curl|bash, --require-hashes installs, wheelhouse-only device deployment, provenance ≠ safe code (TanStack lesson), guard script enforcement, and Ed25519/cryptography alignment with ori-runtime. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
The <9 upper cap on pytest locked the lockfile to 8.4.2, which has a known vulnerability fixed in 9.0.3. Remove the upper cap and set the floor to >=9.0.3. Regenerated requirements-dev.txt — pytest now pins to 9.0.3. pip-audit returns no known vulnerabilities. Co-Authored-By: Claude Sonnet 4.6 <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.
No description provided.