Sweep GitHub for leaked secrets and exposed credentials with git-hound
Search public GitHub broadly for leaked secrets and triage exposures when the workflow is recon and remediation, not generic secret scanning.
What it does
Sweep GitHub for leaked secrets and exposed credentials with git-hound
Search public GitHub broadly for leaked secrets and triage exposures when the workflow is recon and remediation, not generic secret scanning.
Prerequisites
git-hound binary, GitHub token or code search access, and operator-defined dork queries
Installation
Use the upstream install or setup path that matches your environment:
- docker build -t my-githound-container .
- docker run -v /path/to/config.yaml:/root/.githound/config.yaml -v $(pwd)/data:/data my-githound-container --subdomain-file /data/subdomains.txt
Requirements and caveats from upstream:
-
Building the Docker Image
- To build the Docker image for Git-Hound, use the following command:
- This command builds the Docker image with the tag my-githound-container. You can change the tag name to your preference.
Basic usage or getting-started notes:
-
Example config.yaml:
-
Use the following command to run the container with your configuration and input files:
-
Extracted from upstream docs: https://raw.githubusercontent.com/tillson/git-hound/HEAD/README.md
Documentation
Source
Capabilities
Install
Quality
deterministic score 0.45 from registry signals: · indexed on github topic:agent-skills · 8 github stars · SKILL.md body (1,375 chars)