-
Notifications
You must be signed in to change notification settings - Fork 6
Open
Description
Hekkos found 1 Secret Scanning configuration issue in this repository.
This is part of the main security audit.
Issue details
- Issue 1: Secret scanning is not enabled - exposed credentials will not be detected
Why this matters
Secret scanning detects accidentally committed credentials. When secrets are committed:
- They remain in git history even if removed in later commits
- Public repositories expose them to anyone with access
- Automated tools actively scan for exposed credentials to exploit
- Remediation requires rotating credentials and cleaning git history
How to fix
- Navigate to Settings > Code security and analysis
- Enable Secret scanning
- Optionally enable Push protection to prevent secrets from being committed
Documentation:
Reactions are currently unavailable