Skip to content

added gitleaks workflow - #468

Open
0xcucumbersalad wants to merge 1 commit into
mainfrom
add/sast-workflow
Open

added gitleaks workflow#468
0xcucumbersalad wants to merge 1 commit into
mainfrom
add/sast-workflow

Conversation

@0xcucumbersalad

@0xcucumbersalad 0xcucumbersalad commented Aug 14, 2026

Copy link
Copy Markdown
Contributor

added gitleaks workflow


Summary by cubic

Adds a SAST GitHub Actions workflow that runs gitleaks/gitleaks-action on PRs and pushes to main to block leaked secrets. Previously we had no automated secret scanning; now findings fail the check and can gate merges.

  • Triggers on pull_request and on pushes to main; cancels in-progress runs per ref.
  • Scans PR commits on PRs; scans full history on pushes (fetch-depth: 0) to catch rotated-but-committed secrets.
  • Uses pinned SHAs and least-privilege permissions, including pull-requests: read for PR commit access.
  • Required: For organization-owned repos, add a GITLEAKS_LICENSE secret (repo or org level); the job also uses GITHUB_TOKEN.
  • If the check fails, remove the secret from history and rotate the credential before merging.

Written for commit 5bdf438. Summary will update on new commits.

Review in cubic

@0xcucumbersalad
0xcucumbersalad requested a review from a team August 14, 2026 05:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant