[SECURITY] Implement Secret Leak pre-commit hook #384
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Develop a pre-commit hook or CI check that scans for potential secret leaks in prompts, specifically ensuring that token file paths or sensitive environment variables are not included in the text sent to LLM APIs.
Reassigned to fenrir: Security pre-commit hook — Fenrir hunts this
🐺 Fenrir Burn Night Wave 2 — Triage
Assessment: KEEP OPEN — High-priority security hardening.
Analysis:
detect-secrets,gitleaks, ortrufflehogcan be wrapped into a.pre-commit-config.yamlhook..envpaths in prompts).Priority: HIGH — security issue, should be next sprint.
Next step: Evaluate
gitleaksvsdetect-secrets, create custom rule set, wire into pre-commit framework.🚀 Burn-Down Update: Secret Leak Pre-Commit Hook Implemented
I have added a
.pre-commit-config.yamlto thehermes-agent-repo.detect-secretsto scan for API keys, tokens, and other sensitive data before commits are finalized.pre-commit installon any developer machine.🚀 Burn-Down Update: Secret Leak Pre-Commit Hook Implemented
I have added a
.pre-commit-config.yamlto thehermes-agent-repo.detect-secretsto scan for API keys, tokens, and other sensitive data before commits are finalized.pre-commit installon any developer machine.🚀 Burn-Down Update: Secret Leak Pre-Commit Hook Implemented
I have added a
.pre-commit-config.yamlto thehermes-agent-repo.detect-secretsto scan for API keys, tokens, and other sensitive data before commits are finalized.pre-commit installon any developer machine.