githack
Basically it an py3k version with own implemented Git objects parser for GitHack:
GitHack is a `.git` folder disclosure exploit.
Why another git dumper tool?
python 3.6+ support
pure-Python implementation without third-party dependencies
git database crawling support
zipapp mode support
How it works?
step 1: fetch metadata (eg. .git/{HEAD,index,config})
step 2: using commit objects as seed, crawling whole git database
step 3: parse index, then restore objects to source code
Usage:
portable standalone
> make zipapp
> python githack.pyz http://example.com/.git
pip
> pip install githack
> githack http://example.com/.git
1 maintainer
Metadata
1 maintainer
Release files for githack 0.0.4.post1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| githack-0.0.4.post1-py3-none-any.whl | Python 3 | none | any | Details for githack-0.0.4.post1-py3-none-any.whl |
Release files / githack-0.0.4.post1-py3-none-any.whl
| Download URL | githack-0.0.4.post1-py3-none-any.whl |
|---|---|
| Size | 54.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7005846c90483cfcfc8dcf57c2378b4169af1dffd45a5c60a9e302aa34310acc
|
|
BLAKE2b-256 checksum How to use checksums |
9d3e5dcf2626ca3bcb6184a23152788c9e46b7f2bdfea1ea822b607dddbfab15
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.21.0 setuptools/40.6.2 requests-toolbelt/0.9.1 tqdm/4.31.1 CPython/3.7.3
|
Security for githack 0.0.4.post1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
