Skip to main content
Pre-release

This release is a pre-release and may not be stable for production use.

httpperf

An asyncio HTTP client for load testing, built on libcurl.

httpperf was called acurl until version 1.0.

Design

A load-testing client has three jobs: drive as much load as possible from each machine, report the server's response times rather than time spent waiting on the client, and read responses promptly so the server never sees a slow reader. httpperf is built around these.

All network I/O runs in a small C event loop (the vendored ae reactor from Redis) on its own thread, which never takes the GIL. Python hands requests to that thread and collects finished responses through pipes:

asyncio loop ──req_in pipe──▶ curl thread (ae + curl multi) ──▶ sockets
     ▲                               │
     └──────── req_out pipe ◀────────┘

Bytes are read off the wire as they arrive, whatever Python is doing. If Python falls behind, finished responses wait in the pipe rather than in socket buffers, so the client simply sends new requests more slowly, and curl's timings stay accurate. The cost is the hand-off itself, and the curl thread uses roughly one extra core under load. That is deliberate: a spare core is cheap, and response times you can't trust are worthless.

Response.client_lag shows how far Python is behind (see Timings).

Install

pip install httpperf

Wheels are published for Linux on x86_64 and aarch64, for Python 3.9 to 3.15, with glibc 2.34 or later (Ubuntu 22.04, Debian 12, RHEL 9 and later) or musl (Alpine). They include their own libcurl, with HTTP/2 but not HTTP/3.

Anywhere else, including Python 3.8, pip builds from source against the system's libcurl, which needs its development headers and a C compiler. That libcurl decides whether HTTP/3 is available.

sudo apt install libcurl4-openssl-dev   # Debian/Ubuntu
pip install httpperf

Quick start

import asyncio

import httpperf


async def main():
    async with httpperf.Session() as session:
        r = await session.get("https://example.com/")
        print(r.status_code, r.http_version, r.total_time, r.client_lag)


asyncio.run(main())

Sessions are cheap: create one per virtual user or journey. They share a default Engine (the curl thread, the shared connection pool and the TLS cache) unless you pass your own.

API

Session(*, engine=None, ...)

All arguments are keyword-only. A session can be created anywhere, even outside a running asyncio loop.

Argument Default Meaning
engine None The Engine to use. None means the default engine of the asyncio loop the session is first used in, created when first needed and shared by every session in that loop without one.
connections "shared" "shared": the engine's pool. "session": the session's own pool. "none": a new connection for every request.
tls "shared" Where TLS session tickets are kept. "shared": in the engine, so new connections resume their handshake. "session": per session, so each session starts with a full handshake.
http_version "HTTP/2" "HTTP/2": HTTP/2 over TLS when the server offers it, with requests waiting to share one multiplexed connection. Plain http uses HTTP/1.1. "HTTP/1.1": HTTP/1.1 only. "HTTP/3": HTTP/3 over QUIC only, with no fallback, so requests fail if the server does not offer it.
idle_timeout 118 Seconds a connection may sit idle and still be reused.
max_connection_age 0 Seconds after which a connection is no longer reused, however busy it is. 0 means no limit.
max_host_connections 0 Per-session cap on connections per host. Needs connections="session" or "none".
max_connections 0 Per-session cap on connections in use. Needs connections="session" or "none".
cert None (certfile, keyfile) paths for a client certificate, used by every request unless the request overrides it.
timeout None Seconds allowed for each request, from the start of the transfer to the last byte (each redirect hop separately). None or 0 means no limit.
connect_timeout None Seconds allowed to connect, TLS included. None means curl's default of 300 s.
verify False Server certificate checking. False: none, as most load tests want. True: check against the system CA bundle: SSL_CERT_FILE if set, otherwise libcurl's own default, or the usual system locations if it has none. A path: check against that CA bundle. Requests can override it.
json_dumps None Function that turns a json= argument into the request body (str or bytes). None means the engine's.
json_loads None Function that turns the response body (bytes) into the result of json(). None means the engine's.

Proxies come from the environment, as curl reads them: http_proxy (not HTTP_PROXY, which curl ignores for security), https_proxy or HTTPS_PROXY, then all_proxy or ALL_PROXY, with no_proxy or NO_PROXY for exceptions. A session reads them once, when it is created, so later changes apply to new sessions only.

Cookies always belong to the session, whatever the connection settings.

Engine(*, max_host_connections=0, max_total_connections=0, max_idle_connections=1000, json_dumps=..., json_loads=...)

What sessions share: the curl thread, the shared connection pool, the TLS session cache and the limits. Most programs never create one. Create one to set limits, or to keep groups of sessions in separate pools, and pass it to Session(engine=...).

Argument Meaning
max_host_connections Cap on connections per host for the engine's sessions that use the shared pool or no pool. 0 means no limit. httpperf queues requests above it and reports the wait as queue_time.
max_total_connections Cap on all connections for the same sessions. 0 means no limit.
max_idle_connections How many connections each pool keeps (the shared pool, and each session's own pool). Must be at least 1.
json_dumps, json_loads The JSON functions for the engine's sessions, unless a session sets its own. The defaults use the standard library: compact output, and bodies decoded as UTF-8. See JSON.

Each asyncio loop has its own default engine, so sessions without an engine work in any thread, and in each asyncio.run(), without setup. A loop's default engine lasts as long as the loop, and is closed once the loop has been closed and no session uses it.

An engine binds to the asyncio loop running when it is first used, and so does a session. An engine serves one loop at a time, and using it from a second live loop raises RuntimeError. Once its loop is closed, as at the end of asyncio.run(), it binds to the next one and keeps its pool. So a session kept between asyncio.run() calls keeps its connections. To run loops in several threads at once with your own engines, give each thread its own Engine.

engine.close() stops the curl thread and closes the shared pool's connections, and later requests raise RuntimeError. Requests still in flight fail with RequestError, and a ResourceWarning says how many there were. with and async with call close() on exit. An engine that is no longer referenced is closed automatically. See docs/connections.md for how these fit together.

Session methods

  • await session.get(url, **kwargs), and likewise post, put, patch, delete, head and options.
  • await session.request(method, url, **kwargs).
  • session.close(): closes the session's connections once its requests finish. Later requests raise RuntimeError. with and async with call it on exit.
  • session.cookies(): the cookie jar as a dict.
  • session.get_cookie_list(), session.add_cookie_list(cookies), session.erase_all_cookies() and session.erase_session_cookies(): work with Cookie objects. These are ordinary methods, not coroutines.
  • session.set_response_callback(callback): called with each Response, including each hop of a redirect.

Request arguments

Argument Meaning
params Query parameters: a dict or list of pairs (lists as values repeat the key), or a ready-made string. Added to any query already in the URL.
headers Dict of headers.
headers_list List of "Name: value" strings, for repeated headers.
cookies Dict of cookies to send with this request (added to the session jar).
cookie_list List of Cookie objects.
auth (username, password) for basic auth.
data Request body: str or bytes as is, or a dict or list of pairs, form-encoded with Content-Type: application/x-www-form-urlencoded unless you set it.
json Object to send as JSON, encoded with the session's json_dumps. Sets Content-Type: application/json unless you set it.
files Dict (or list of pairs) of files to send as multipart/form-data, with any data dict as extra fields. A value is an open file, or (filename, content) or (filename, content, content_type), where content is bytes, str or a file. Files are read into memory.
cert (certfile, keyfile), overriding the session's certificate.
verify True, False or a CA bundle path, overriding the session's verify.
timeout, connect_timeout Override the session's. timeout=0 removes the session's limit for this request.
allow_redirects Follow redirects (default True; False for head).
max_redirects Default 5. Raises RequestError("Max Redirects") beyond it.

Failed transfers raise httpperf.RequestError with curl's detailed error message, such as Failed to connect to 127.0.0.1 port 8080 after 0 ms: Couldn't connect to server. Its code is curl's error code. Timeouts raise httpperf.Timeout, a subclass, so they can be counted separately.

Response

Attribute Meaning
status_code HTTP status.
ok True if the status is below 400.
reason Reason phrase from the status line, or the standard phrase for HTTP/2 and HTTP/3, which send none.
raise_for_status() Raises httpperf.HTTPError (a RequestError, with the response) for 4xx and 5xx statuses.
elapsed total_time as a timedelta.
url Effective URL.
redirect_url Location of a redirect, or None.
history Earlier responses in a redirect chain.
http_version "HTTP/1.0", "HTTP/1.1", "HTTP/2" or "HTTP/3".
headers Case-insensitive mapping of the response headers. Repeated headers are joined with , , as in requests. headers_tuple keeps repeats and order. Both skip interim responses such as 100 Continue. header is the raw text of every header block, decoded as latin-1.
body Bytes.
text Body decoded with encoding.
encoding From the Content-Type charset, else latin-1 (utf-8 for JSON). Can be set.
json() Body parsed with the session's json_loads, once. By default the standard library, always as UTF-8, as RFC 8259 requires.
cookies, cookielist The session's cookie jar at the time you read it (not only the cookies this response set). Empty once the session is closed.
primary_ip Address connected to.
upload_size, download_size Bytes, as integers.
request The Request: method, url, headers, cookies, auth, data.

JSON

By default httpperf uses the standard library's json: compact output for json=, and response bodies decoded as UTF-8 for json(). It needs no extra dependency and has the most scrutinised parser, which matters because load tests often fetch responses from third parties.

If JSON costs too much CPU, pass faster functions as json_dumps and json_loads, on the Engine for all its sessions or on one Session. orjson is a good choice for encoding, and pysimdjson for decoding. Create the parser once, at module scope, since it keeps its buffers between documents:

import httpperf
import orjson
import simdjson

parser = simdjson.Parser()
engine = httpperf.Engine(json_dumps=orjson.dumps, json_loads=parser.parse)


async def journey():
    async with httpperf.Session(engine=engine) as session:
        r = await session.post("https://example.com/search", json={"q": "httpperf"})
        return r.json()["items"][3]["name"]

Things to know:

  • orjson is about 8 times faster than json on larger payloads, but turns NaN into null and refuses integers over 64 bits.
  • parser.parse is lazy: only the values you touch become Python objects. That was about 8 times faster than json.loads for reading one field of a 500 KB document. The result is read-only and not a real dict or list; .as_dict() and .as_list() convert it. Documents stay valid after the parser moves on to the next one.
  • To get real dicts and lists from simdjson, use json_loads=lambda body: parser.parse(body, True).
  • Request bodies that never change can be encoded once and sent as data=, with headers={"Content-Type": "application/json"}.

Timings

All in seconds.

Attribute Meaning
start_time, end_time Wall-clock times (time.time()) when the request was made and when Python received the response.
namelookup_time DNS, measured by curl from the start of the transfer.
connect_time TCP connect complete. 0 when the connection was reused.
appconnect_time TLS handshake complete. 0 for plain http and reused connections.
pretransfer_time Ready to send.
posttransfer_time Request fully sent. starttransfer_time − posttransfer_time is the server's time to first byte, without connection setup or upload. None with libcurl older than 8.10.
starttransfer_time First byte received.
total_time Transfer complete.
queue_time Time waiting in httpperf's queue for a connection, under the engine or session limits. 0 if the request did not wait. curl's timings start after it.
client_lag end_time − start_time − total_time − queue_time: time the request spent waiting on Python, before it was sent and after it finished. Measured with the monotonic clock, so clock changes don't affect it.

curl measures its timings on the curl thread, so a busy Python process does not inflate them. client_lag is how you see that Python is the bottleneck: if it grows, the client cannot keep up, and achieved request rates describe the client rather than the server. Report it alongside response times (p50, p99, max).

queue_time is real waiting that a user would see (a browser's "stalled" time), but it is client-side, so keep it out of server latency.

Known limitations

  • curl closes expired idle connections lazily, the next time the pool needs a connection, so the server sees the close late. See docs/connections.md.
  • Requests in flight when Engine.close() is called never complete.

Development

make test
make lint               # ruff and clang-format, check only
make lint-fix           # apply formatting and fixes
make clean              # remove build output, caches and profiler output (keeps .venv)
make distclean          # also remove .venv

Each target first creates .venv with uv, if needed, and installs httpperf in editable mode with the dev tools. It reinstalls when setup.py, pyproject.toml or the C sources change, so C edits are rebuilt automatically. make venv does only that step.

make venv PY_VERSION=3.8 VENV=.venv-3.8 builds another venv, and VENV=.venv-3.8 on make test or make lint uses it.

To release, set __version__ in httpperf/version.py (for example 1.0rc1 or 1.0), commit and push to main, then run make release. It tags v<version> and pushes the tag, and the release workflow builds the wheels and publishes them to PyPI.

The tests run local servers: pytest-httpbin, small threaded http.server servers for connection counting and TLS, and hypercorn for HTTP/2 and HTTP/3 (skipped on Python 3.8, where hypercorn's HTTP/3 server hangs on shutdown). Client certificates are generated with openssl. The httpbin server is single-threaded, so keep concurrency in tests low.

Set HTTPPERF_PROFILE=1 when building to instrument the extension. See docs/profiling.md.

Licence

MIT. See LICENSE. NOTICE covers the bundled Redis event library and the libraries included in the binary wheels.

Metadata

Release files for httpperf 1.0rc1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for httpperf 1.0rc1
File Size Uploaded Provenance Actions
httpperf-1.0rc1.tar.gz 59.8 kB With provenance Details for httpperf-1.0rc1.tar.gz

Built distributions (wheels)

Table of built distributions (wheels) for httpperf 1.0rc1
File Actions
httpperf-1.0rc1-cp315-cp315-musllinux_1_2_x86_64.whl CPython 3.15 CPython 3.15 Linux musl 1.2+ x86-64 Details for httpperf-1.0rc1-cp315-cp315-musllinux_1_2_x86_64.whl
httpperf-1.0rc1-cp315-cp315-musllinux_1_2_aarch64.whl CPython 3.15 CPython 3.15 Linux musl 1.2+ ARM64 Details for httpperf-1.0rc1-cp315-cp315-musllinux_1_2_aarch64.whl
httpperf-1.0rc1-cp315-cp315-manylinux_2_34_x86_64.whl CPython 3.15 CPython 3.15 Linux glibc 2.34+ x86-64 Details for httpperf-1.0rc1-cp315-cp315-manylinux_2_34_x86_64.whl
httpperf-1.0rc1-cp315-cp315-manylinux_2_34_aarch64.whl CPython 3.15 CPython 3.15 Linux glibc 2.34+ ARM64 Details for httpperf-1.0rc1-cp315-cp315-manylinux_2_34_aarch64.whl
httpperf-1.0rc1-cp314-cp314-musllinux_1_2_x86_64.whl CPython 3.14 CPython 3.14 Linux musl 1.2+ x86-64 Details for httpperf-1.0rc1-cp314-cp314-musllinux_1_2_x86_64.whl
httpperf-1.0rc1-cp314-cp314-musllinux_1_2_aarch64.whl CPython 3.14 CPython 3.14 Linux musl 1.2+ ARM64 Details for httpperf-1.0rc1-cp314-cp314-musllinux_1_2_aarch64.whl
httpperf-1.0rc1-cp314-cp314-manylinux_2_34_x86_64.whl CPython 3.14 CPython 3.14 Linux glibc 2.34+ x86-64 Details for httpperf-1.0rc1-cp314-cp314-manylinux_2_34_x86_64.whl
httpperf-1.0rc1-cp314-cp314-manylinux_2_34_aarch64.whl CPython 3.14 CPython 3.14 Linux glibc 2.34+ ARM64 Details for httpperf-1.0rc1-cp314-cp314-manylinux_2_34_aarch64.whl
httpperf-1.0rc1-cp313-cp313-musllinux_1_2_x86_64.whl CPython 3.13 CPython 3.13 Linux musl 1.2+ x86-64 Details for httpperf-1.0rc1-cp313-cp313-musllinux_1_2_x86_64.whl
httpperf-1.0rc1-cp313-cp313-musllinux_1_2_aarch64.whl CPython 3.13 CPython 3.13 Linux musl 1.2+ ARM64 Details for httpperf-1.0rc1-cp313-cp313-musllinux_1_2_aarch64.whl
httpperf-1.0rc1-cp313-cp313-manylinux_2_34_x86_64.whl CPython 3.13 CPython 3.13 Linux glibc 2.34+ x86-64 Details for httpperf-1.0rc1-cp313-cp313-manylinux_2_34_x86_64.whl
httpperf-1.0rc1-cp313-cp313-manylinux_2_34_aarch64.whl CPython 3.13 CPython 3.13 Linux glibc 2.34+ ARM64 Details for httpperf-1.0rc1-cp313-cp313-manylinux_2_34_aarch64.whl
httpperf-1.0rc1-cp312-cp312-musllinux_1_2_x86_64.whl CPython 3.12 CPython 3.12 Linux musl 1.2+ x86-64 Details for httpperf-1.0rc1-cp312-cp312-musllinux_1_2_x86_64.whl
httpperf-1.0rc1-cp312-cp312-musllinux_1_2_aarch64.whl CPython 3.12 CPython 3.12 Linux musl 1.2+ ARM64 Details for httpperf-1.0rc1-cp312-cp312-musllinux_1_2_aarch64.whl
httpperf-1.0rc1-cp312-cp312-manylinux_2_34_x86_64.whl CPython 3.12 CPython 3.12 Linux glibc 2.34+ x86-64 Details for httpperf-1.0rc1-cp312-cp312-manylinux_2_34_x86_64.whl
httpperf-1.0rc1-cp312-cp312-manylinux_2_34_aarch64.whl CPython 3.12 CPython 3.12 Linux glibc 2.34+ ARM64 Details for httpperf-1.0rc1-cp312-cp312-manylinux_2_34_aarch64.whl
httpperf-1.0rc1-cp311-cp311-musllinux_1_2_x86_64.whl CPython 3.11 CPython 3.11 Linux musl 1.2+ x86-64 Details for httpperf-1.0rc1-cp311-cp311-musllinux_1_2_x86_64.whl
httpperf-1.0rc1-cp311-cp311-musllinux_1_2_aarch64.whl CPython 3.11 CPython 3.11 Linux musl 1.2+ ARM64 Details for httpperf-1.0rc1-cp311-cp311-musllinux_1_2_aarch64.whl
httpperf-1.0rc1-cp311-cp311-manylinux_2_34_x86_64.whl CPython 3.11 CPython 3.11 Linux glibc 2.34+ x86-64 Details for httpperf-1.0rc1-cp311-cp311-manylinux_2_34_x86_64.whl
httpperf-1.0rc1-cp311-cp311-manylinux_2_34_aarch64.whl CPython 3.11 CPython 3.11 Linux glibc 2.34+ ARM64 Details for httpperf-1.0rc1-cp311-cp311-manylinux_2_34_aarch64.whl
httpperf-1.0rc1-cp310-cp310-musllinux_1_2_x86_64.whl CPython 3.10 CPython 3.10 Linux musl 1.2+ x86-64 Details for httpperf-1.0rc1-cp310-cp310-musllinux_1_2_x86_64.whl
httpperf-1.0rc1-cp310-cp310-musllinux_1_2_aarch64.whl CPython 3.10 CPython 3.10 Linux musl 1.2+ ARM64 Details for httpperf-1.0rc1-cp310-cp310-musllinux_1_2_aarch64.whl
httpperf-1.0rc1-cp310-cp310-manylinux_2_34_x86_64.whl CPython 3.10 CPython 3.10 Linux glibc 2.34+ x86-64 Details for httpperf-1.0rc1-cp310-cp310-manylinux_2_34_x86_64.whl
httpperf-1.0rc1-cp310-cp310-manylinux_2_34_aarch64.whl CPython 3.10 CPython 3.10 Linux glibc 2.34+ ARM64 Details for httpperf-1.0rc1-cp310-cp310-manylinux_2_34_aarch64.whl
httpperf-1.0rc1-cp39-cp39-musllinux_1_2_x86_64.whl CPython 3.9 CPython 3.9 Linux musl 1.2+ x86-64 Details for httpperf-1.0rc1-cp39-cp39-musllinux_1_2_x86_64.whl
httpperf-1.0rc1-cp39-cp39-musllinux_1_2_aarch64.whl CPython 3.9 CPython 3.9 Linux musl 1.2+ ARM64 Details for httpperf-1.0rc1-cp39-cp39-musllinux_1_2_aarch64.whl
httpperf-1.0rc1-cp39-cp39-manylinux_2_34_x86_64.whl CPython 3.9 CPython 3.9 Linux glibc 2.34+ x86-64 Details for httpperf-1.0rc1-cp39-cp39-manylinux_2_34_x86_64.whl
httpperf-1.0rc1-cp39-cp39-manylinux_2_34_aarch64.whl CPython 3.9 CPython 3.9 Linux glibc 2.34+ ARM64 Details for httpperf-1.0rc1-cp39-cp39-manylinux_2_34_aarch64.whl

Total release size: 96.6 MB

Release files / httpperf-1.0rc1.tar.gz

Download URL httpperf-1.0rc1.tar.gz
Size 59.8 kB
Tags Source
SHA-256 checksum
How to use checksums
1ebaf2646ee58bfb2cbcee92ab524dae3564730549eed4fc63c3844273dce9f5
BLAKE2b-256 checksum
How to use checksums
df734f2c639ea6cf1c96f7efd93bf8f81f8f87513ab73b0c3ca0e3a45f8b7b91
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 12, 2026.

Transparency log

Release files / httpperf-1.0rc1-cp315-cp315-musllinux_1_2_x86_64.whl

Download URL httpperf-1.0rc1-cp315-cp315-musllinux_1_2_x86_64.whl
Size 3.2 MB
Tags CPython 3.15 Linux musl 1.2+ x86-64
SHA-256 checksum
How to use checksums
73dec849767d1a8ca91129489c92200a2810be3052e2afcf74bd33c8d671adce
BLAKE2b-256 checksum
How to use checksums
052719020c681587f73acd8da55522020020e0eeb99ef30efae3b13916683051
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 12, 2026.

Transparency log

Release files / httpperf-1.0rc1-cp315-cp315-musllinux_1_2_aarch64.whl

Download URL httpperf-1.0rc1-cp315-cp315-musllinux_1_2_aarch64.whl
Size 3.5 MB
Tags CPython 3.15 Linux musl 1.2+ ARM64
SHA-256 checksum
How to use checksums
623d3cb68c5515f76e66f2cb923ad284a175eda95da3268ccc0346f9d3e1849a
BLAKE2b-256 checksum
How to use checksums
56270b94897b5f0375d2f21faa98011cd54c58631e867651f6609e7ffdc110c9
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 12, 2026.

Transparency log

Release files / httpperf-1.0rc1-cp315-cp315-manylinux_2_34_x86_64.whl

Download URL httpperf-1.0rc1-cp315-cp315-manylinux_2_34_x86_64.whl
Size 3.6 MB
Tags CPython 3.15 Linux glibc 2.34+ x86-64
SHA-256 checksum
How to use checksums
a3d439bbbd534cdf4b1cec18ad1160003d6191a649eaea3494a7c6ba3f5611b6
BLAKE2b-256 checksum
How to use checksums
c750abd2f42af63b90ead644631146fd2e7b4c57ad3a557d65899268f34d907b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 12, 2026.

Transparency log

Release files / httpperf-1.0rc1-cp315-cp315-manylinux_2_34_aarch64.whl

Download URL httpperf-1.0rc1-cp315-cp315-manylinux_2_34_aarch64.whl
Size 3.4 MB
Tags CPython 3.15 Linux glibc 2.34+ ARM64
SHA-256 checksum
How to use checksums
4bc7b7302603822f4a5b3164f7d3800e06f668d218754fad2a870a351b1b5cb0
BLAKE2b-256 checksum
How to use checksums
9ce5bd8d65508f83e95e04b999a63ba833d31cf865ef454380dad68a42741704
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 12, 2026.

Transparency log

Release files / httpperf-1.0rc1-cp314-cp314-musllinux_1_2_x86_64.whl

Download URL httpperf-1.0rc1-cp314-cp314-musllinux_1_2_x86_64.whl
Size 3.2 MB
Tags CPython 3.14 Linux musl 1.2+ x86-64
SHA-256 checksum
How to use checksums
b60e9af9d82188ae801f3f8e2cf3d1226679cd5868b9d76fc504ed86ec3fe90c
BLAKE2b-256 checksum
How to use checksums
27563da2114add0430f6423b559317221a2d03950691524379317273e8bdf628
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 12, 2026.

Transparency log

Release files / httpperf-1.0rc1-cp314-cp314-musllinux_1_2_aarch64.whl

Download URL httpperf-1.0rc1-cp314-cp314-musllinux_1_2_aarch64.whl
Size 3.5 MB
Tags CPython 3.14 Linux musl 1.2+ ARM64
SHA-256 checksum
How to use checksums
4a97b72079ad27ccee87a36bf9f88b03c18a52e8b1dda091afa22c773a68bba3
BLAKE2b-256 checksum
How to use checksums
9547e45561ff911d796c3297be6ff71c46b251490c23d0cc15d65a5c5adf4152
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 12, 2026.

Transparency log

Release files / httpperf-1.0rc1-cp314-cp314-manylinux_2_34_x86_64.whl

Download URL httpperf-1.0rc1-cp314-cp314-manylinux_2_34_x86_64.whl
Size 3.6 MB
Tags CPython 3.14 Linux glibc 2.34+ x86-64
SHA-256 checksum
How to use checksums
97c8e7e5ac6156ce204bd38eccb899d17c1572767ac522912da7acefb8ce6ceb
BLAKE2b-256 checksum
How to use checksums
73d045609faaba95f4b59bf5f3993497a570cc0bb1bfb8ba568479ebe30ebbc8
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 12, 2026.

Transparency log

Release files / httpperf-1.0rc1-cp314-cp314-manylinux_2_34_aarch64.whl

Download URL httpperf-1.0rc1-cp314-cp314-manylinux_2_34_aarch64.whl
Size 3.4 MB
Tags CPython 3.14 Linux glibc 2.34+ ARM64
SHA-256 checksum
How to use checksums
3d9723968c85bcbfc8d371c7d9532ef686c7bd7155a2930d53ac0d8bf673d955
BLAKE2b-256 checksum
How to use checksums
cfa1ee9351578b6df324dc8a2a8fcda37085139bf8669e3785b7457fa7478369
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 12, 2026.

Transparency log

Release files / httpperf-1.0rc1-cp313-cp313-musllinux_1_2_x86_64.whl

Download URL httpperf-1.0rc1-cp313-cp313-musllinux_1_2_x86_64.whl
Size 3.2 MB
Tags CPython 3.13 Linux musl 1.2+ x86-64
SHA-256 checksum
How to use checksums
3c7a98b63bf2cd66806a33d766751c66f059b7c2c7d57de3fa625b9dca654f3e
BLAKE2b-256 checksum
How to use checksums
61f4a248f10a0fcef6b6317081bc2e2851a56b16f71b8988b429ecfa666712af
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 12, 2026.

Transparency log

Release files / httpperf-1.0rc1-cp313-cp313-musllinux_1_2_aarch64.whl

Download URL httpperf-1.0rc1-cp313-cp313-musllinux_1_2_aarch64.whl
Size 3.5 MB
Tags CPython 3.13 Linux musl 1.2+ ARM64
SHA-256 checksum
How to use checksums
63d39cbfca95794f58de24dbe0dd1831a94fbbe01d3d3afd18e8a1f79e66f06f
BLAKE2b-256 checksum
How to use checksums
d07ef59f3f2fbc8b85fa01ce9681ab1d7d25fa79cdea32895e2eb2d9e15a485f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 12, 2026.

Transparency log

Release files / httpperf-1.0rc1-cp313-cp313-manylinux_2_34_x86_64.whl

Download URL httpperf-1.0rc1-cp313-cp313-manylinux_2_34_x86_64.whl
Size 3.6 MB
Tags CPython 3.13 Linux glibc 2.34+ x86-64
SHA-256 checksum
How to use checksums
ca015da0ebcd21c5d9370cfbd865f281a5c57e488daf8b3ace6bf35654863534
BLAKE2b-256 checksum
How to use checksums
a25ea0af0a2c2c55bb5e507b49e8527e900fe5424621afc0ab77dd466f919831
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 12, 2026.

Transparency log

Release files / httpperf-1.0rc1-cp313-cp313-manylinux_2_34_aarch64.whl

Download URL httpperf-1.0rc1-cp313-cp313-manylinux_2_34_aarch64.whl
Size 3.4 MB
Tags CPython 3.13 Linux glibc 2.34+ ARM64
SHA-256 checksum
How to use checksums
78fd02b57fcdffb396c5df39d09790cb67b703bdfc0b3e459a5f43f0ad0b0054
BLAKE2b-256 checksum
How to use checksums
aef2a02c2162498190f985c0322ca6d72e8773993e27ea94a8be434412344238
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 12, 2026.

Transparency log

Release files / httpperf-1.0rc1-cp312-cp312-musllinux_1_2_x86_64.whl

Download URL httpperf-1.0rc1-cp312-cp312-musllinux_1_2_x86_64.whl
Size 3.2 MB
Tags CPython 3.12 Linux musl 1.2+ x86-64
SHA-256 checksum
How to use checksums
05c5d5775500f772b2e0f340591ff759e1fcdf2592a6f928349457086c291323
BLAKE2b-256 checksum
How to use checksums
bc303ebf095b5d4cf1635c4f716e52bbdb23accd03a92bdf27060e9720b35aee
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 12, 2026.

Transparency log

Release files / httpperf-1.0rc1-cp312-cp312-musllinux_1_2_aarch64.whl

Download URL httpperf-1.0rc1-cp312-cp312-musllinux_1_2_aarch64.whl
Size 3.5 MB
Tags CPython 3.12 Linux musl 1.2+ ARM64
SHA-256 checksum
How to use checksums
ece24cd132db0acebbd83bf43803f61f0a7ffa95850470cb232f526efacc420f
BLAKE2b-256 checksum
How to use checksums
0c8dab5af70dae64b1a724aafd87bd10f5c26dcdb8a360cc1f64f2f01966ecf7
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 12, 2026.

Transparency log

Release files / httpperf-1.0rc1-cp312-cp312-manylinux_2_34_x86_64.whl

Download URL httpperf-1.0rc1-cp312-cp312-manylinux_2_34_x86_64.whl
Size 3.6 MB
Tags CPython 3.12 Linux glibc 2.34+ x86-64
SHA-256 checksum
How to use checksums
b0953a524c3ba4911e0528d36b9e1a0b25b17135e5e21a8f468979040b3b9a41
BLAKE2b-256 checksum
How to use checksums
8d5e5cb751f327be721ea05414a4865d470ab57497e908e2903b131f8e7dcd1a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 12, 2026.

Transparency log

Release files / httpperf-1.0rc1-cp312-cp312-manylinux_2_34_aarch64.whl

Download URL httpperf-1.0rc1-cp312-cp312-manylinux_2_34_aarch64.whl
Size 3.4 MB
Tags CPython 3.12 Linux glibc 2.34+ ARM64
SHA-256 checksum
How to use checksums
481f1cab12251f97dc9b4e5c1e33474657fa9ea6034c5deaf6f9b9afe7f2ce09
BLAKE2b-256 checksum
How to use checksums
972622599ab27555de41cb362a213840815fdc1db29df46b3f4745213eff9381
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 12, 2026.

Transparency log

Release files / httpperf-1.0rc1-cp311-cp311-musllinux_1_2_x86_64.whl

Download URL httpperf-1.0rc1-cp311-cp311-musllinux_1_2_x86_64.whl
Size 3.2 MB
Tags CPython 3.11 Linux musl 1.2+ x86-64
SHA-256 checksum
How to use checksums
be8d9344f86ae1ba8601821b7ce5fd3eeef0d63e4b2e32e7d275fd60b1f5f707
BLAKE2b-256 checksum
How to use checksums
868979ec0cb55509be12333bac299fc5fabbed880a24d4722513cbb1bb79f9db
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 12, 2026.

Transparency log

Release files / httpperf-1.0rc1-cp311-cp311-musllinux_1_2_aarch64.whl

Download URL httpperf-1.0rc1-cp311-cp311-musllinux_1_2_aarch64.whl
Size 3.5 MB
Tags CPython 3.11 Linux musl 1.2+ ARM64
SHA-256 checksum
How to use checksums
17259cbf1c01463ab511311b7628de7b4bd3c0d8f5baac3e82f72bf12acb9e40
BLAKE2b-256 checksum
How to use checksums
aedabba36df306eff0461152ee4ac33ad78053ca476c136d7fcb5b935889557a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 12, 2026.

Transparency log

Release files / httpperf-1.0rc1-cp311-cp311-manylinux_2_34_x86_64.whl

Download URL httpperf-1.0rc1-cp311-cp311-manylinux_2_34_x86_64.whl
Size 3.6 MB
Tags CPython 3.11 Linux glibc 2.34+ x86-64
SHA-256 checksum
How to use checksums
95f8b00e797e7f3e6c6a7a75136e25868fae07b96bb729414839a115143a7fc9
BLAKE2b-256 checksum
How to use checksums
838a890e56e545813762dd01b76ad79280c34c8f1aa8e1a55a60a8b193690b69
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 12, 2026.

Transparency log

Release files / httpperf-1.0rc1-cp311-cp311-manylinux_2_34_aarch64.whl

Download URL httpperf-1.0rc1-cp311-cp311-manylinux_2_34_aarch64.whl
Size 3.4 MB
Tags CPython 3.11 Linux glibc 2.34+ ARM64
SHA-256 checksum
How to use checksums
4162089e15bd197663fbe85c5a289318d37b9a081e4a596354513e3db015d33a
BLAKE2b-256 checksum
How to use checksums
7c0a4ac59a2dd6f33222f249dedf831eca78f61b53f9fde35d411eb9ed3e2f74
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 12, 2026.

Transparency log

Release files / httpperf-1.0rc1-cp310-cp310-musllinux_1_2_x86_64.whl

Download URL httpperf-1.0rc1-cp310-cp310-musllinux_1_2_x86_64.whl
Size 3.2 MB
Tags CPython 3.10 Linux musl 1.2+ x86-64
SHA-256 checksum
How to use checksums
20ec77c884c9a33fb90c644817b0580186032764c0d193e6a66abe9ff0231f38
BLAKE2b-256 checksum
How to use checksums
a6a742f85c18303409c7f4a3bee02423699dd6a72e8a9ca292c5ff3cd88b013d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 12, 2026.

Transparency log

Release files / httpperf-1.0rc1-cp310-cp310-musllinux_1_2_aarch64.whl

Download URL httpperf-1.0rc1-cp310-cp310-musllinux_1_2_aarch64.whl
Size 3.5 MB
Tags CPython 3.10 Linux musl 1.2+ ARM64
SHA-256 checksum
How to use checksums
1587b6e310ee6159942808b4ab5c95dfa5dfcd1ee69ac9379c5c17d4337ee828
BLAKE2b-256 checksum
How to use checksums
566c505cef223b1bdb7d5d457898b8006a261efadcd3e26c11b5fe1bb5cf571c
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 12, 2026.

Transparency log

Release files / httpperf-1.0rc1-cp310-cp310-manylinux_2_34_x86_64.whl

Download URL httpperf-1.0rc1-cp310-cp310-manylinux_2_34_x86_64.whl
Size 3.6 MB
Tags CPython 3.10 Linux glibc 2.34+ x86-64
SHA-256 checksum
How to use checksums
efcb80a91d5c304836c53d220eb8d82656a5745a64ea3a39accd781344d3a8d2
BLAKE2b-256 checksum
How to use checksums
2d8c024dc11ea9d8d4ad8c0159067061853b9c3c87299b6e729b7310ea85568c
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 12, 2026.

Transparency log

Release files / httpperf-1.0rc1-cp310-cp310-manylinux_2_34_aarch64.whl

Download URL httpperf-1.0rc1-cp310-cp310-manylinux_2_34_aarch64.whl
Size 3.4 MB
Tags CPython 3.10 Linux glibc 2.34+ ARM64
SHA-256 checksum
How to use checksums
92bcc3ac5229c630246e6e75111c73fe45e251d9d5a23b57541a154951b5df9e
BLAKE2b-256 checksum
How to use checksums
a3493b1fada3634ed517254593bb8843c6f20816f28b47ea6b47511cdddc89ed
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 12, 2026.

Transparency log

Release files / httpperf-1.0rc1-cp39-cp39-musllinux_1_2_x86_64.whl

Download URL httpperf-1.0rc1-cp39-cp39-musllinux_1_2_x86_64.whl
Size 3.2 MB
Tags CPython 3.9 Linux musl 1.2+ x86-64
SHA-256 checksum
How to use checksums
f5b6bd5846c9598138f98918c0440c7717834c727dd8c7b35580af235fa1503f
BLAKE2b-256 checksum
How to use checksums
95054d39d5b0e08e3486967f5bf96497ffc2a6ad708819700138890cbff395e7
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 12, 2026.

Transparency log

Release files / httpperf-1.0rc1-cp39-cp39-musllinux_1_2_aarch64.whl

Download URL httpperf-1.0rc1-cp39-cp39-musllinux_1_2_aarch64.whl
Size 3.5 MB
Tags CPython 3.9 Linux musl 1.2+ ARM64
SHA-256 checksum
How to use checksums
b4a4b2c743e1a3e645202f22cecf01ae98201d6aa646d768f31f1ef11cd0cd99
BLAKE2b-256 checksum
How to use checksums
f62698ef707e70eb904a6a584cdb6258c1d84e656472af1fb23fe2ce36f0bf5d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 12, 2026.

Transparency log

Release files / httpperf-1.0rc1-cp39-cp39-manylinux_2_34_x86_64.whl

Download URL httpperf-1.0rc1-cp39-cp39-manylinux_2_34_x86_64.whl
Size 3.6 MB
Tags CPython 3.9 Linux glibc 2.34+ x86-64
SHA-256 checksum
How to use checksums
90e36925bd33fa42d4b343ee64142fc3ccc5355e16bac7056564b2e18d35a7d3
BLAKE2b-256 checksum
How to use checksums
20d26e3be19c42a273ca08c26cfe5b9710621decdfb70d7f763fbc9b1d3768b1
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 12, 2026.

Transparency log

Release files / httpperf-1.0rc1-cp39-cp39-manylinux_2_34_aarch64.whl

Download URL httpperf-1.0rc1-cp39-cp39-manylinux_2_34_aarch64.whl
Size 3.4 MB
Tags CPython 3.9 Linux glibc 2.34+ ARM64
SHA-256 checksum
How to use checksums
f00b190e992240ea1d050fbf91fe0efe474c4d2c1a995e312bbcd66cbb636007
BLAKE2b-256 checksum
How to use checksums
86dbe687811c005f3d2f998079d0552c381bb153af8684f69af8c42aab200edc
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 12, 2026.

Transparency log

Security for httpperf 1.0rc1

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.

Full provenance

All 29 files in this release have been uploaded with provenance metadata.

Select from 29 files

Attestation for httpperf-1.0rc1.tar.gz

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 Nov 12, 2026.

Transparency log

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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page