security: harden the dependency and CI/CD supply chain#30
Merged
Conversation
Addresses the supply-chain findings from the dependency security review. - Dependabot auto-merge: gate on update-type so only patch/minor bumps are auto-approved+merged; never auto-merge GitHub Actions updates. A green CI run is no longer treated as evidence that a new dependency release is trustworthy. - Pin every GitHub Actions `uses:` to a full commit SHA (version in a trailing comment) instead of a mutable @vn tag, across all workflows. Most important for the third-party softprops/action-gh-release used in the privileged release job. - Enable Gradle dependency verification (gradle/verification-metadata.xml, sha256 for 633 components across the full build+test graph) so a swapped dependency, plugin, or build-script artifact fails resolution. Validated by a clean `build test` run with verification enforced. - Pin the Gradle distribution: add distributionSha256Sum to the wrapper, and add a gradle/actions/wrapper-validation step in CI to verify gradle-wrapper.jar. - Add actions/dependency-review-action as a PR gate (fail-on-severity: high) to block newly introduced dependencies with known high-severity advisories. - Extend Dependabot to the npm ecosystem (the published browser SDK and each demo's Playwright e2e suite), which were previously unmonitored. - Document the build/distribution trust boundary and these mitigations in docs/threat-model.md (new "Supply chain" section + 4th trust boundary). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
wolpert
force-pushed
the
security/supply-chain-hardening
branch
from
June 6, 2026 14:50
39414f0 to
712a014
Compare
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.
Addresses the supply-chain findings from the dependency security review. All six recommendations plus a threat-model update, in one commit.
Changes
uses:pinned to a full commit SHA (version in a trailing comment) instead of a mutable@vNtag, across all workflows. Most important for the third-partysoftprops/action-gh-releasein the privileged release job.gradle/verification-metadata.xmlpins sha256 for 633 components across the full build+test graph, so a swapped dependency/plugin/build-script artifact fails resolution.distributionSha256Sumon the wrapper + agradle/actions/wrapper-validationstep in CI.actions/dependency-review-actionwithfail-on-severity: high.Validation
clean build testtwice. The generation run wasBUILD SUCCESSFULend-to-end; the enforcement re-run wasBUILD SUCCESSFUL in 51swith zero dependency-verification failures (Postgres + DynamoDB integration tests executed, so their runtime deps are captured).NoClassDefFoundErrorflake (unrelated to these changes); the subsequent run passed.Requires repo-settings action (cannot be done in code)
SECURITY.md"Report a vulnerability" path.dependency-review-action(default on for public repos).🤖 Generated with Claude Code