loading
Loading content
loading
Discovery
Recover incomplete git repositories from dumped .git folders.
overview
gittools-extractor is the recovery half of the GitTools project. It takes a dumped .git folder, the raw objects, refs, and index, and reconstructs the repository's source files from them. Every commit it can rebuild is written out, so you get readable code rather than the opaque git internals the dumper left behind.
It is built to handle incomplete dumps. When a download came back partial because the server hid or dropped some objects, the Extractor recovers as many files and commits as the available objects support, which is often enough to expose configuration and secrets. That makes it the natural follow-on when gittools-dumper returns a repository that is not fully intact.
On Trickest, gittools-extractor is a Discovery node that takes a dumped git folder and writes a folder of reconstructed source. Place it right after gittools-dumper, then route the rebuilt tree into a secret scanner to triage what the exposure leaked.
use cases
Feed the Extractor a folder of dumped .git objects and it reconstructs the commits into readable source files you can review.
When the dumper returned an incomplete repository, the Extractor rebuilds as many files as the available objects allow rather than failing outright.
Pass the reconstructed source to a tool like gitleaks so credentials buried in the recovered history get surfaced and triaged.
Because each commit rebuilds into its own numbered folder, you can trace when a secret was introduced or which files changed across the exposed timeline.
reference
| Name | Type | Flag | Description |
|---|---|---|---|
| git-folder | FOLDER | · | Dumped .git repository folder to reconstruct from (typically gittools-dumper output). |
Showing key inputs. gittools-extractor exposes 1 inputs in total.
example
# reconstruct source from a dumped .git folderextractor.sh ./dumped-git ./recovered############ Extractor is part of https://github.com/internetwache/GitTools## Developed and maintained by @gehaxelt from @internetwache###########[+] Found commit: 7f3c9a2e5d1b8046af2c9d3e1b0a5c47e9d28f61[+] Found file: /recovered/0-7f3c9a2e5d1b8046af2c9d3e1b0a5c47e9d28f61/config.php[+] Found file: /recovered/0-7f3c9a2e5d1b8046af2c9d3e1b0a5c47e9d28f61/.env[+] Found commit: 4b8e1d60c7a2f9538e0b6c1a4d7f2093ab5e6c82[+] Found file: /recovered/1-4b8e1d60c7a2f9538e0b6c1a4d7f2093ab5e6c82/config.phpguidance
Use gittools-extractor after a .git directory has been dumped to a folder, when you want the readable source back. It reconstructs, it does not download, so it pairs with gittools-dumper upstream. For download plus recovery in one node, use gittools-dumper-extractor.
The download half of GitTools; run it first to produce the folder this tool reconstructs from.
Combines downloading and reconstruction in one step when you have a live target URL.
Downloads and rebuilds an exposed repo directly from a URL rather than from a dumped folder.
faq
related
Check whether a URL redirects to a masked 404 page.
Append lines to a file only if they are not already there.
Extract URLs and endpoints from Android APK files.
Visual inspection of websites across a large number of hosts.
Find suspicious files across a large set of AWS S3 buckets.
An automated tool that checks for backup artifacts that may disclose a web application's source code.
A dumped .git folder feeds gittools-extractor, which reconstructs the commits and writes the recovered source as a queryable output.
Facts on this page come from the live Trickest tool library.