SK-3102-gitleaks-detection-fix

[skyflow-himanshupal]

Resolves Gitleaks security scan failures by removing hardcoded token values from test files and example code in README.md.

Why

• Security Compliance: Automated Gitleaks scans detected hardcoded tokens and high-entropy secret patterns in test suites and documentation.
• Underlying Issue: Mock credentials and sample tokens used in tests and README.md triggered security scanner alerts.
• Intent: Clear CI/CD security checks while adhering to proper secret handling practices.

Goal

• Intended Outcome: Pass all automated Gitleaks scans in CI/CD pipelines.
• Working Functionality: Ensure tests continue to run properly using sanitized dummy placeholders or mock environment variables, and README.md displays safe example tokens.
• Non-Goals: Modifying core production application logic or secret rotation (as exposed values were only test/example tokens).

Testing

• Only the hard coded tokens were changed and no additional unit tests are required.
• Deployment Concerns: None. No production code logic was altered.

Tech Debt

• Addressing Tech Debt: Reduces security tech debt by removing hard coded credentials from documentation and tests, setting a clean pattern for future code examples.

[github-actions]

✅ Gitleaks Findings: No secrets detected. Safe to proceed!

[github-actions]

Semgrep Findings: Issues with Error level severity are found (Error is Highest severity in Semgrep), Please resolve the issues before merging.

[github-actions]

✅ Gitleaks Findings: No secrets detected. Safe to proceed!

[github-actions]

Semgrep Findings: Issues with Error level severity are found (Error is Highest severity in Semgrep), Please resolve the issues before merging.