Security hardening: remove demo key, sanitize env examples, add secret scanning #226
Conversation
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
…nd replace committed private key with placeholder - Replace real-looking secrets in workflow/.env.example with placeholders and warnings - Add .github/SECURITY.md with Safe Harbor and private reporting guidance - Add templates/ssl_cert/.gitignore and README; replace demo key with placeholder - Aligns with BugBounty.md guidance on responsible disclosure and secret handling
…ample - Add .gitleaks.toml and GitHub Actions workflow to scan secrets on PR/push - Add workflow/.env.production.example with SANDBOXED defaults and secret-manager placeholders
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.
This PR addresses findings from a source-level security audit aligned with BugBounty.md.
Summary
Recommended follow-ups (not included here)
Please review.