Strake Gate Check
Version updated for https://github.com/strake-dev/gate-check to version v1.1.0.
- This action is used across all versions by ? repositories.
Action Type
This is a Composite action.
Go to the GitHub Marketplace to find the latest changes.
Action Summary
The strake-dev/gate-check GitHub Action provides a pre-deployment safety mechanism by integrating the Strake gate engine into CI workflows. It automates the evaluation of pull requests, assigns a “go,” “hold,” or “critical” verdict, and optionally blocks merges based on the assessment. This action streamlines the deployment process by enforcing safety checks directly within the CI/CD pipeline and providing feedback through PR comments.
What’s Changed
Signal 5 — Dependency Change Detection
The Strake gate now flags suspicious dependency changes between builds. Catches the gap vulnerability scanners and SBOMs miss: the window between a malicious package publish and your next deploy.
What’s new
- GO / HOLD / CRITICAL verdicts now factor in dependency changes detected via lockfile diff at the deploy boundary
- Auto-HOLD on critical patterns: new dependency published <24h ago, version changed to one published <2h ago, lockfile deleted, registry URL swapped
- Warnings on suspicious-but-not-critical patterns: major version bumps not tied to PR code changes, transitive-only changes, lockfile drift from CI