ci: supply-chain hardening to raise OSSF Scorecard / HVTrust#684
Merged
Conversation
Maps OSSF Scorecard + provenance/signing changes to HVTracker's HVTrust scoring model. Covers Scorecard publishing, hardening files, Renovate with SHA pinning, enforced commit signing, and SLSA release artifacts. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…lish action - build-artifacts needs contents: write for 'gh release upload' - pin pypa/gh-action-pypi-publish to release/v1 SHA (Pinned-Dependencies) Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool. What Enabling Code Scanning Means:
For more information about GitHub Code Scanning, check out the documentation. |
blove
added a commit
that referenced
this pull request
Jun 18, 2026
…low guard (#687) The supply-chain-hardening guard (scripts/ci-workflow.spec.mjs) added in #684 asserts every workflow sets a top-level DO_NOT_TRACK=1, but release-provenance.yml was missed — so the 'Validate CI workflow guards' check fails on every PR. Add the env block; guard test now passes 11/11. Co-authored-by: Claude Fable 5 <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
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
Closes the supply-chain evidence gaps that suppress threadplane's HVTracker HVTrust score. The dominant lever is the OSSF Scorecard (feeds both Safety ×0.5 and Transparency ×0.5 of HVTrust); commit/release signing and provenance feed the rest. All changes are genuine hardening — no score gaming.
publish_results: true(public OpenSSF API + README badge)javascript-typescript+python(SAST check)permissions:on the 3 publish workflows (Token-Permissions)Spec:
docs/superpowers/specs/2026-06-18-hvtrust-supply-chain-hardening-design.mdPlan:
docs/superpowers/plans/2026-06-18-hvtrust-supply-chain-hardening.mdActivation steps (not in this PR — maintainer/account actions)
required_signaturesonmain(do signing first)renovate.jsonSCORECARD_TOKENsecret to unlock the Branch-Protection checkTest Plan
actionlintclean (only pre-existing shellcheck info)🤖 Generated with Claude Code