Use case
Find leaked secrets in git history
A removed secret still lives in your history. OpenRouting scans the whole history, so leaks don't hide in old commits.
Illustrative example — the key is redacted before any AI review.
In short: OpenRouting runs Gitleaks over your working tree and your full git history, so a key that was committed and later deleted is still found. Secret values are redacted before any AI review, and each finding gets an explanation and a suggested fix.
The latest commit isn't the whole story
When you delete a key from a file and commit, the old commit with the key is untouched and still reachable by anyone who can clone the repo. Scanning only the working tree misses it entirely.
Scan history, redact before AI
OpenRouting runs Gitleaks across your git history as part of a scan. Found secrets are surfaced as findings — and their values are redacted before anything is sent to the review model, so the secret is handled by the scanner and never leaves with the prompt.
What to do when a secret is found
If a credential has been committed:
- Rotate it first — treat it as compromised.
- Purge it from history if needed, and coordinate the force-push with your team.
- Scope the blast radius: what could the key reach, and was it used?
Questions
Does deleting a secret from a file fix it?
No. Git keeps history, so a key committed earlier is still readable in old commits. Rotate the credential, then purge it from history if needed.
Does OpenRouting scan git history?
Yes. It runs Gitleaks across your history, so a secret that was removed from the current files but never rotated still shows up.
Are my secrets sent to an AI model?
No. Secret values are redacted before any code is sent for AI review. The scanner handles the secret; the model never sees it.