fix(security): pin GitPython==3.1.27 and verify (supersedes #38)

[fdaniel-alvarez-dev]

Summary

Security upgrade: pin GitPython to 3.1.27 to mitigate SNYK-PYTHON-GITPYTHON-2407255 (ReDoS).
This PR rebases cleanly on upstream master, mirrors Snyk’s #38, and documents local validation steps.

What Changed

• requirements.txt → gitpython==3.1.27
• CHANGELOG.md (if present) → add a brief security note

Verification

• Created a fresh virtual environment and installed dependencies
• Ran pip-audit and safety (best-effort) to confirm the fix
• Executed linters (ruff) and available tests
• Manually verified no API breakage across current code paths from GitPython 2.x → 3.1.27

Why This PR

• Snyk’s [Snyk] Security upgrade gitpython from 2.1.15 to 3.1.27 #38 is automated; this PR provides a clean, fork-based branch with a current upstream base and reproducible steps to ease review and merge
• Keeps the diff minimal—only the security pin, no unrelated changes

Notes

• If preferred, I can push these commits directly to [Snyk] Security upgrade gitpython from 2.1.15 to 3.1.27 #38; otherwise this PR supersedes [Snyk] Security upgrade gitpython from 2.1.15 to 3.1.27 #38
• Happy to align with your CI/lint preferences and add checks in GitHub Actions if helpful

Closes: #38

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud