hate_crack (PyPI name placeholder — not the tool)
This is not an installable copy of hate_crack. pip install hate-crack will
fail on purpose. The name is held here only so nobody else can publish under it,
because a package claiming to be an offensive security tool would be installed
with an expectation of trust, often on a host holding client hash material and
API credentials.
hate_crack is installed from source:
git clone https://github.com/trustedsec/hate_crack
cd hate_crack
make install
Full instructions: https://github.com/trustedsec/hate_crack#installation
Why there is no real distribution
hate_crack is not self-contained in the way a wheel requires:
- It builds compiled helpers (hashcat-utils, princeprocessor, OMEN) from git submodules, which would need a per-platform build matrix or a C toolchain on every target.
HashcatRosettais reached through asys.pathinsertion relative to the repository, not as a declared dependency.- Self-update is git-native (
git checkoutplusmake install), so a site-packages copy could not update itself. - hashcat, wordlists, and rules still have to be installed separately, so a single-command install would not actually be single-command.
Metadata
Release files for hate-crack 0.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| hate_crack-0.0.0.tar.gz | 2.7 kB | Details |
Release files / hate_crack-0.0.0.tar.gz
| Download URL | hate_crack-0.0.0.tar.gz |
|---|---|
| Size | 2.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b7fecf797f1b4cdde0290cb73ac6955ac60c6c59a8e6f4204fa6248b4c546517
|
|
BLAKE2b-256 checksum How to use checksums |
a2b94d3f45ba56c0cc7b765c30d079978f5f575986df3c2145de2becddf9b89f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 31, 2026.
Transparency log