Built configurable secret-detection rules with severity-based enforcement; integrated pre-commit and CI checks and generated JSON/HTML reports for secure-development review.
How I built it & what I contributed
- Security problem
I built a Python tool to identify secrets and API keys in development work. The goal is to make potential credential exposure visible while code is being prepared and reviewed.
- Configurable detection
I implemented configurable detection rules rather than relying on one fixed check. This makes the tool adaptable to different secret patterns and development-review needs.
- Severity-based enforcement
I added severity-based enforcement so findings can be handled according to their assigned importance. This connects detection with a decision about whether a development step should proceed.
- Developer workflow integration
I integrated checks into pre-commit and CI workflows, including GitHub Actions. This places secret review within the existing Git workflow rather than requiring a separate manual scan every time.
- Reports for review
I generated JSON and HTML reports to make findings usable in both automated processing and human review. The project connects Python detection logic, Git integration, and reporting in a secure-development workflow.