Find the identities and exposures hidden in git history.
What it does
Investigate repository history and public code-host data to produce cited findings about developer identities, infrastructure and credential exposure.
When to use it
Use for developer or organisation investigations, suspected credential leaks, and secrets removed from current code but retained in history or forks.
How to use it
Give it an investigation target or suspected leak; it returns findings documented with repository, commit SHA, date and file path.
Uses
Good to know
- cannot be undone: security contacts
What you need · 5
Requires trufflehog for the instructed full-history scan alongside gitleaks.
Requires gitleaks for the instructed second secret scanner.
Access · 7
This skill
security contacts
Sends credential exposure reports (irreversible)
credential-provider APIs
Submits credentials for live verification