Use it
Add the index next to PyPI. pip looks at both and takes a wheel from here where it fits your platform and PyPI has none:
pip install --extra-index-url https://wheelgap.github.io/tracker/wheels/simple/ PACKAGE
Each wheel is for one release. If PyPI has a newer release with no wheel for your platform, pip builds that one from source; add --prefer-binary to take the wheel here instead.
pip only, for now: uv ranks an extra index above PyPI and, for a version found here, would see only this one Windows wheel and none of PyPI's files.
What is checked
- It is built from the sdist PyPI publishes for that release (its sha256 is checked against PyPI's). Build tools come from PyPI too, and a build may download more (Rust crates, for example).
- It is built twice, in two separate GitHub Actions runs, and published only when both builds are byte-identical. A build that isn't reproducible, or that something changed in one run only, is never published.
- It carries exactly one tag, the Python and platform it was built and tested on, and every DLL its extension modules import is either beside them in the wheel or one every Windows machine with that Python has.
- It is installed into a fresh environment on a fresh runner of its platform and imported; on free-threaded Python the GIL must stay off. That checks the wheel works; it isn't a security check.
- The index carries each file's sha256, which pip checks. Each file has an attestation that the tracker's gap-wheels workflow published it:
gh attestation verify FILE.whl -R wheelgap/tracker. - Every published wheel, with its sdist's sha256 and links to both build runs, is in gap-wheels.json.
What it can't promise: a wheel is exactly as trustworthy as the sdist it was built from, since building the package yourself runs the same code. Only releases whose PyPI metadata names an OSI-approved licence (or the PSF licence Python itself uses) are published, and for now only Windows wheels: a Linux wheel needs its libraries bundled and a manylinux or musllinux tag first.
Maintainers
These wheels stand in until your release ships its own; when it does, tell us in an issue and ours come down. If you'd rather we didn't publish wheels of your project at all, open an opt-out issue: we take them down by hand, and the weekly batch keeps them out. Want the build that worked here? Each row links to both build runs.
Published wheels
| Package | Version | Target | Verified | Builds | File |
|---|---|---|---|---|---|
| fastuuid | 0.14.0 | 3.14 win-arm64 | 2026-11-16 | build 1, build 2 | wheel |
| hypothesis | 6.170.15 | 3.14t win-arm64 | 2026-11-16 | build 1, build 2 | wheel |
| lz4 | 4.4.5 | 3.14t win-arm64 | 2026-11-16 | build 1, build 2 | wheel |
| ormsgpack | 1.13.1 | 3.14t win-arm64 | 2026-11-16 | build 1, build 2 | wheel |
| polars-runtime-32 | 2.1.0 | 3.14t win-arm64 | 2026-11-16 | build 1, build 2 | wheel |
| pyiceberg | 0.12.0 | 3.14 win-arm64 | 2026-11-16 | build 1, build 2 | wheel |
| rpds-py | 2026.9.1 | 3.14t win-arm64 | 2026-11-16 | build 1, build 2 | wheel |
| safetensors | 0.8.0 | 3.14t win-arm64 | 2026-11-16 | build 1, build 2 | wheel |
| setproctitle | 1.3.8 | 3.14 win-arm64 | 2026-11-16 | build 1, build 2 | wheel |
| setproctitle | 1.3.8 | 3.14t win-arm64 | 2026-11-16 | build 1, build 2 | wheel |
| tokenizers | 0.23.3 | 3.14t win-arm64 | 2026-11-16 | build 1, build 2 | wheel |
| zstandard | 0.25.0 | 3.14t win-arm64 | 2026-11-16 | build 1, build 2 | wheel |