pepe
HTTP load generator and latency tool, one binary: a load test with a live
dashboard, pepe ping (a request a second, split into DNS, connect, TLS,
first byte and download), pepe ramp (find the capacity), pepe api (an
OpenAPI spec), pepe flow (a sequence of requests), pepe replay (an
access log), pepe compare (two reports). The documentation is at
pepe.mhaimdat.com/docs.
pipx install pepe-http # or: pip install pepe-http
pepe https://example.com
pepe is written in Rust, and this package is the pepe command that
fetches it: the first run downloads the release of the same version for
your platform (macOS, Linux, Windows) from
GitHub releases, checks
it against the SHA-256 the release carries, keeps it in your cache
directory (~/.cache/pepe-http, ~/Library/Caches/pepe-http on macOS,
%LOCALAPPDATA%\pepe-http\Cache on Windows; PEPE_HTTP_CACHE_DIR moves
it) and runs it; every later run only runs it. There are no dependencies.
python -m pepe_http is the same command.
Upgrade with pipx upgrade pepe-http or pip install -U pepe-http: each
version of the package runs the pepe of that version, so pepe self-update does not apply here. The other ways to install, with tab
completion and man pages, are on the
install page.
As an MCP server, uvx pepe-http mcp (or pepe mcp) serves pepe's modes
as tools; it is listed in the MCP registry as io.github.omarmhaimdat/pepe.
1 maintainer
Metadata
1 maintainer
Release files for pepe-http 0.45.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 | |
|---|---|---|---|
| pepe_http-0.45.0.tar.gz | 6.0 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pepe_http-0.45.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 12.4 kB
Release files / pepe_http-0.45.0.tar.gz
| Download URL | pepe_http-0.45.0.tar.gz |
|---|---|
| Size | 6.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4133f8f2440eb0a63a0596ce93a8984e9535162ce0e0817de6fc7d01ae44f760
|
|
BLAKE2b-256 checksum How to use checksums |
47ee6a2f4ca63e8d1515edb4d060fad11487efc688b2e6073e077e70de49d719
|
| 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 Oct 17, 2026.
Transparency logRelease files / pepe_http-0.45.0-py3-none-any.whl
| Download URL | pepe_http-0.45.0-py3-none-any.whl |
|---|---|
| Size | 6.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
146717fcceee2c2799d985f068cd7bc091a32e17e623104830a4d29fe496aab5
|
|
BLAKE2b-256 checksum How to use checksums |
4b4cd027e057a0ad528acf30a4c2571e60d46802cb28b9eef93563da204b58f0
|
| 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 Oct 17, 2026.
Transparency log
