Hysen Labs
Open-source project
WangYihang/GitHacker avatar
WangYihang

GitHacker

🕷️ A `.git` folder exploiting tool that is able to restore the entire Git repository, including stash, common branches and common tags.

1,664 stars247 forksPythonLicense varies
DEEP OPEN-SOURCE ANALYSIS

GitHacker: 🕷️ A `.git` folder exploiting tool that is able to restore the entire Git repository, including stash, common branches and common tags.

🕷️ A `.git` folder exploiting tool that is able to restore the entire Git repository, including stash, common branches and common tags.

What the project is

GitHacker is a Python project hosted on GitHub. 🕷️ A `.git` folder exploiting tool that is able to restore the entire Git repository, including stash, common branches and common tags. A multi-threaded .git folder exploitation tool. Reconstructs the target repository in full . source code, commit history, branches, stashes, remotes, tags . even when DirectoryListings is disabled, by brute-forcing well-known refs. The repository is maintained by WangYihang and tracks activity through its public issue tracker and commit history. Readers who want a working example rather than a bare library will find the documentation and the linked resources useful for getting a first build running.

What it offers

The GitHacker repository documents several concrete capabilities that shape how people use it. A reproducible Benchmark against six other pillagers (GitTools, dvcs-ripper, GitHack, git-dumper, dumpall, rbozburun/git-hacker) across five web-server scenarios. An adversarial Security suite that runs every tool against malicious .git/ directories and tracks coordinated disclosure of findings. Methodology and Reproduce pages with every detail needed to re-run the use locally. .git/ folder attack . comparison of attack tools, Part I Git Repository Layout These points are taken from the project README, so they reflect what the maintainers actually ship rather than marketing claims. Checking the file list and the example directories gives a fuller picture of how each piece fits together.

How to set it up

Getting GitHacker running starts with cloning the source from https://github.com/WangYihang/GitHacker. The README lists the commands needed to fetch the code and build or launch it. Representative steps from the documentation include: docker run -v $(pwd)/results:/tmp/githacker/results \ docker run wangyihang/githacker --help docker run -v $(pwd)/results:/tmp/githacker/results \ docker run -v $(pwd)/results:/tmp/githacker/results \. After the code is on disk, the project instructions walk through configuration and any dependencies. Following the order shown in the README avoids the common setup mistakes that come from mixing steps.

License and project status

GitHacker is written primarily in Python and is released under the an unstated license license, which sets the terms for reuse and redistribution. The project reports around 1664 stars on GitHub, a signal of how many developers have bookmarked it. The source was last updated on 2026-08-21. The canonical location is https://github.com/WangYihang/GitHacker, where the license file, the changelog and the open issues give the most current state of the work. Anyone planning to depend on it should read the license text directly before shipping it inside another product.

Editorial conclusion

The GitHacker source lives at https://github.com/WangYihang/GitHacker under the an unstated license license and is mainly written in Python. The README and the linked examples remain the place to confirm the current behaviour before adopting the project.

DEEP OPEN-SOURCE ANALYSIS

Official sources

Community notes

Community notes