Add secret scanning protection with Gitleaks#214
Merged
dev-fatima-24 merged 2 commits intoApr 29, 2026
Merged
Conversation
- Add GitHub Actions workflow for CI/CD secret scanning - Add pre-commit hook configuration to block local commits - Add custom gitleaks config for Stellar keys, JWT secrets, API tokens - Add setup scripts for Linux/macOS and Windows - Add comprehensive documentation - Update README with setup instructions Implements multi-layered protection against accidental credential commits. Covers Stellar secret keys, JWT secrets, private keys, and API tokens.
|
@ayomidearegbeshola29-dev Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
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
2 participants
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.
closes #102
✅ Task Completed Successfully!
I've successfully implemented secret scanning protection for your VacciChain repository. Here's what was done:
🎯 What Was Implemented
GitHub Actions Workflow (
gitleaks.yml
)
Automatically scans for secrets on every push and PR to main/develop
Blocks PRs if secrets are detected
Uploads detailed reports for investigation
Pre-commit Hook Configuration (.pre-commit-config.yaml)
Blocks commits containing secrets locally before they reach GitHub
Provides immediate feedback to developers
Custom Gitleaks Configuration (.gitleaks.toml)
Detects Stellar secret keys (S...)
Detects JWT secrets
Detects API tokens and private keys
Allowlist for false positives (test files, examples, docs)
Setup Scripts
setup-git-hooks.sh
for Linux/macOS
setup-git-hooks.ps1
for Windows
One-command setup for all developers
Documentation (
secret-scanning-setup.md
)
Complete setup guide
Usage instructions
Troubleshooting tips
Updated README with setup instructions
📦 Branch & Commit
✅ Created branch: feature/add-secret-scanning-protection
✅ Committed all changes (8 files, 596 insertions)
✅ Pushed to GitHub successfully