GitDorker Documentation

GitDorker uses the GitHub Search API, which is limited to 30 requests per minute. While the tool has a built-in sleep function to prevent failures, you can optimize performance by providing multiple tokens.

Recommendation: Provide at least two GitHub personal access tokens in your token file. GitDorker will alternate between them during the dorking process, reducing the likelihood of hitting rate limits. Using tokens from separate GitHub accounts provides the best results.

GitDorker requires Python 3 and a GitHub Personal Access Token to function. To set up the environment locally:

1. Ensure Python 3 is installed.
2. Obtain a GitHub Personal Access Token (refer to GitHub's guide if needed).
3. Install the necessary dependencies using pip:

pip3 install -r requirements.txt

If you prefer using Docker, you can build and run the tool in a containerized environment.

Build the image:

docker build -t gitdorker .

Basic run (interactive):

docker run -it gitdorker

Full run with volume mapping: To ensure your tokens and dorks are accessible inside the container, map your local directory to /tf inside the container:

docker run -it -v $(pwd)/tf:/tf gitdorker -tf tf/TOKENSFILE -q tesla.com -d dorks/DORKFILE -o tesla

The following arguments are used by the GitDorker.py script:

You can run GitDorker directly using the GitDorker.py script. Use the following flags to specify your tokens, search query, dork file, and output name:

• -tf: Path to the file containing your GitHub Personal Access Tokens.
• -q: The search query (e.g., a domain like tesla.com).
• -d: Path to the dorks file (e.g., Dorks/DORKFILE).
• -o: The output prefix/name for the results.

Example usage:

python3 GitDorker.py -tf TOKENSFILE -q tesla.com -d Dorks/DORKFILE -o tesla