feat: Security Improvements (CodeQL, DAST, Log Redaction)

[Miyamura80]

Summary

This PR implements several security enhancements identified in the Agent Readiness Report:

1. Log Scrubbing: Implemented PII redaction (email, API keys) in src/utils/logging_config.py using loguru's patcher.
2. Static Analysis: Added a CodeQL workflow (.github/workflows/codeql.yml) scanning Python and TypeScript.
3. Dynamic Analysis: Added a DAST workflow (.github/workflows/dast.yml) using OWASP ZAP (manual trigger).

[github-advanced-security]

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.

[greptile-apps]

Greptile Overview

Greptile Summary

This PR implements comprehensive security improvements including log scrubbing for PII redaction, CodeQL static analysis, and infrastructure for DAST scanning.

Key Changes:

• Implemented PII redaction in logging that scrubs emails, API keys (OpenAI, Anthropic, Stripe), Bearer tokens, and generic API keys from both log messages and exception messages
• Pre-compiled regex patterns for performance optimization
• Exception handling properly re-instantiates exceptions with redacted messages to preserve loguru's formatting expectations
• Added CodeQL workflow for automated security scanning of Python and TypeScript code
• Comprehensive test coverage verifies all PII patterns are correctly redacted

Code Quality:
The implementation addresses all previously raised concerns including exception scrubbing, pattern pre-compilation, and comprehensive test coverage. The exception handling correctly preserves the exception instance structure expected by loguru by re-instantiating exceptions rather than storing strings.

Confidence Score: 5/5

• This PR is safe to merge with comprehensive security improvements and thorough testing
• All previously identified issues have been properly addressed: PII patterns are pre-compiled for performance, exception handling correctly re-instantiates exception objects to preserve loguru formatting, comprehensive test coverage validates all redaction patterns, and the implementation follows project coding standards
• No files require special attention

Important Files Changed

Filename	Overview
.github/workflows/codeql.yml	Added CodeQL static analysis workflow scanning Python and TypeScript on push, PR, and weekly schedule
pyproject.toml	Updated vulture exclusions to explicitly list test files instead of using wildcard pattern
src/utils/logging_config.py	Implemented comprehensive PII redaction for logs including emails, API keys (OpenAI, Anthropic, Stripe), Bearer tokens, and generic keys - scrubs both messages and exceptions
tests/test_logging_security.py	Added comprehensive test coverage for PII redaction functionality covering all supported patterns and exception handling

[greptile-apps]

_{2 files reviewed, 2 comments}

_{Edit Code Review Agent Settings | Greptile}

[greptile-apps]

_{1 file reviewed, 1 comment}

_{Edit Code Review Agent Settings | Greptile}

[greptile-apps]

_{1 file reviewed, 1 comment}

_{Edit Code Review Agent Settings | Greptile}

[greptile-apps]

_{3 files reviewed, 3 comments}

_{Edit Code Review Agent Settings | Greptile}

[greptile-apps]

_{1 file reviewed, 1 comment}

_{Edit Code Review Agent Settings | Greptile}

[gitguardian]

⚠️ GitGuardian has uncovered 4 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
26449490	Triggered	Bearer Token	cd71987	tests/test_logging_security.py	View secret
26449491	Triggered	Generic High Entropy Secret	cd71987	tests/test_logging_security.py	View secret
26449492	Triggered	Generic High Entropy Secret	cd71987	tests/test_logging_security.py	View secret
26448353	Triggered	Generic High Entropy Secret	451e5b0	tests/test_logging_security.py	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[greptile-apps]

_{1 file reviewed, 1 comment}

_{Edit Code Review Agent Settings | Greptile}

[greptile-apps]

_{1 file reviewed, 1 comment}

_{Edit Code Review Agent Settings | Greptile}

[greptile-apps]

_{1 file reviewed, 1 comment}

_{Edit Code Review Agent Settings | Greptile}

[greptile-apps]

_{1 file reviewed, 1 comment}

_{Edit Code Review Agent Settings | Greptile}

[greptile-apps]

_{1 file reviewed, 1 comment}

_{Edit Code Review Agent Settings | Greptile}