Integration
Use GitHub Actions as the enforcement point.
ShakerScan fits into GitHub checks by returning policy decisions and evidence links that can be required before merge.
Sample gate decision
Required GitHub check failed
The ShakerScan check reports a blocked AI Gate decision. Branch protection prevents merge until the finding is fixed or approved.
Trigger the workflow on pull_request or deployment events.
Run shakerscan ai gate with expected scope fields.
Verify the attestation and policy decision.
Publish an evidence-aware check result and block when policy fails.
Why ShakerScan
The output is a release control, not just a report.
ShakerScan is built around release evidence: a tested target, a policy result, a verifier command, and an approval path when risk needs human review.
Signed evidence
Evidence hashes and AI Gate attestations bind the decision to the target, environment, policy, probe pack, and release scope when signing is configured.
CI-verifiable decision
GitHub Actions or the shakerscan CLI can verify that the decision matches the expected repo, commit, branch, environment, target, policy, and evidence hash.
Approval workflow
When an eligible workflow is approved, scoped approval tokens record the reason, audience, expiry, and decision path instead of bypassing the gate silently.
Checklist
Workflow checklist
Store API keys in GitHub secrets.
Pass repo and commit metadata explicitly.
Require the check on protected branches.
Use environment protection rules for production gates.
Limitations
What this page does not claim
ShakerScan does not replace human security review, threat modeling, or a scoped penetration test.
AI Gate decisions depend on the configured target, probe pack, policy, scan profile, and available evidence.
Production targets require authorization, safe scope, rate limits, and operational approval.
FAQ
Is ShakerScan an AI pentesting replacement?
No. ShakerScan is a verifiable security gate for release workflows. It complements deeper manual testing by producing repeatable runtime evidence and CI-verifiable allow, block, or needs_approval decisions.
Can ShakerScan scan any target?
No. Targets must be owned by the customer or explicitly authorized. Production scans should use safe profiles, rate limits, and defined scope.