{"repo":"nyancrimew/goop","free":true,"listed":false,"github":"https://github.com/nyancrimew/goop","clone":"git clone https://github.com/nyancrimew/goop.git","description":"Yet another tool to dump a git repository from a website, focused on as-complete-as-possible dumps and handling weird edge-cases.","language":"Go","stars":654,"topics":["git","infosec","offensive-security","bug-bounty"],"license":"MIT","category":"security-tools","readme_excerpt":"goop Yet another tool to dump a git repository from a website. goop tries to focus on as-complete-as-possible dumps and handling as many edge-cases as possible, compared to other tools, which seem to focus on bare minimum dumps. Original codebase heavily inspired by arthaud/git-dumper. Usage Example Installation How does it work? The tool will first check if directory listing is available. If it is, then it will just recursively download the .git directory (what you would do with wget ). If directory listing is not available, it will use several methods to find as many files as possible. Step by step, goop will: Fetch all common files ( .gitignore , .git/HEAD , .git/index , etc.); Find as many refs as possible (such as refs/heads/master , refs/remotes/origin/HEAD , etc.) by analyzing .git/HEAD , .git/logs/HEAD , .git/config , .git/packed-refs and so on; Find as many objects (sha1) as possible by analyzing .git/packed-refs , .git/index , .git/refs/ and .git/logs/ ; Fetch all objects recursively, analyzing each commits to find their parents; Run git checkout . to recover the current working tree; Attempt to fetch missing files listed in the git index; Attempt to create objects for manually fetched files; Attempt to fetch files listed in .gitignore","default_branch":null,"files":null,"tree":[],"storefront":"/r/nyancrimew","claimed":false,"request_supported":{"post":"https://gitbuyer.com/r/nyancrimew/goop/request-supported","requests":0},"note":"indexed from public GitHub; nothing is for sale on this page. Clone it from GitHub. Paid listings live at /search."}