onyxweb
URL in, fully-rendered HTML out. A Rust + Chromium (CDP) engine with a typed Python API, built for high-throughput recon, scraping, and change detection.
No Node process like Playwright, no WebDriver like Selenium. One install, one process, ~8.5 URL/s.
Installation
uv add onyxweb # or: pip install onyxweb
uv run onyxweb --install # one-time: fetch the pinned chrome-headless-shell (~180 MB)
Python 3.10+. Wheels for linux (x86_64, aarch64), macOS (arm64), Windows x64. Anything else builds from source and needs rustup.
Embedding onyxweb in another tool? await onyxweb.aensure_chrome(dest=...) installs the browser wherever you want and returns the path for Client(chrome_path=...); find_chrome() is a no-network "is it installed?" check.
Quickstart
import onyxweb
r = onyxweb.fetch("https://example.com") # rendered HTML, post-JS
png = onyxweb.screenshot("https://example.com") # png / jpeg / webp
both = onyxweb.fetch_all("https://example.com") # both, from one page visit
r.title # "Example Domain"
r.text # visible text; script and style source left out
r.links, r.images, r.scripts # lazy buckets of records (see Page buckets)
# CSS + BeautifulSoup-style queries, parsed and run in Rust
r.dom.find_all("a", limit=10)
RenderResult is not a str. Pass r.html to regex, lxml, or BS4. str(r), "x" in r, and len(r) still work.
Examples
1) Sweep a lot of URLs
with onyxweb.Client(concurrency=16) as c:
for r in c.batch(urls, capture="html"):
if isinstance(r, Exception): # batch never raises; failures land in place
continue
print(r.status_code, r.title)
2) Async, or N threads on one Client
async with onyxweb.AsyncClient(concurrency=16) as ac:
results = await asyncio.gather(*(ac.fetch(u) for u in urls))
The GIL is released for all Rust work, so a thread pool over one Client runs genuinely parallel.
3) Get past a WAF
from onyxweb.presets.full import stealth
with onyxweb.Client(**stealth.BASIC) as c: # real Chrome, automation tells stripped
r = c.fetch("https://www.tesla.com/")
4) Drive the page before capture
r = client.fetch(
url,
scripts=[HOOK_JS], # runs before any page script
post_load_scripts=["document.title"], # returns land in r.post_load_results
actions=[onyxweb.Click(selector="#login")], # CDP-trusted click / fill / hover / wait
block_urls=["*://*.tracker.example/*"],
extra_headers={"Referer": "https://ref.example/"},
)
Per-call settings are reverted before the tab returns to the pool, so nothing leaks between fetches.
Page buckets
A captured page is sorted into 9 lazy buckets: scripts, styles, links, images, iframes, forms, meta, comments, json_ld. Sizing or printing one costs nothing until you read its records.
r.overview(prnt=True) # count and size of every bucket, no records built
r.content.scripts # inline half: source that lives in the document
r.resources.scripts # external half: URLs the page loads
r.resources.all() # everything the browser fetches, in document order
r.scripts.search("apiKey") # records containing a string, matched in Rust
r.scripts.matches(r'"apiKey":"(\w+)"', regex=True)[0].value # just the captured key
Every URL-bearing record carries url (absolute) and raw (as authored). Search patterns use Rust's regex crate: linear time, no lookaround.
Anti-bot
r.anti_bot is populated on every fetch, whether or not you try to get past anything, so a plain fetch tells you a host sits behind Akamai.
r.anti_bot # AntiBot(vendor="cloudflare", kind="challenge", resolved=True) or None
bypass_anti_bot=True waits out challenge interstitials and self-heals hard blocks by dropping only the anti-bot cookies, then retrying once. Vendor-agnostic (Akamai, Cloudflare, DataDome, PerimeterX, Imperva).
In testing the full engine cleared Akamai, DataDome, PerimeterX, and Cloudflare on sites like tesla.com and ticketmaster. It does not beat Kasada or an interactive captcha, and says so through .anti_bot instead of handing back a challenge stub.
Two engines
onyxweb.Client(engine="shell") # default: bundled chrome-headless-shell, fast and light
onyxweb.Client(engine="full") # real Chrome, --headless=new, beats WAFs the shell can't
Presets
Spread into Client(...). Organized engine-first, since the two engines want opposite recipes.
| Preset | When to use it |
|---|---|
full.stealth.BASIC |
Akamai/Cloudflare-class WAFs (needs a full Chrome binary) |
shell.stealth.BASIC |
naive JS bot checks, not a real WAF bypass |
shell.stealth.FINGERPRINT |
BASIC plus WebGL vendor override and canvas noise |
shell.recon.FAST |
subdomain sweeps: JS off, 5 s timeout, ad/tracker blocklist |
shell.archival.FULL_PAGE |
change-detection snapshots of SPA-heavy sites |
onyxweb --preset list # print every preset and exit
The response
Every result carries the whole HTTP response, shaped to match blasthttp so it drops straight into BBOT's HTTP_RESPONSE.
r.metadata.status_code, r.metadata.protocol, r.metadata.remote_ip
r.metadata.redirect_chain, r.metadata.cert_info, r.metadata.body_hashes
r.headers["content-type"], r.headers.cookies, r.headers.raw
Hashes (md5 / mmh3 / sha256) are computed in Rust and match Python's hashlib and mmh3.hash() byte for byte.
CLI
onyxweb https://example.com # HTML to stdout
onyxweb https://example.com -o page.html -s shot.png
onyxweb https://example.com --json # HTML + metadata as JSON
onyxweb --help # every config knob is a flag
Configuration
Flat kwargs, a ClientConfig object, or ONYXWEB_* environment variables.
onyxweb.Client(viewport=(1920, 1080), locale="en-GB", proxy="http://user:pass@host:8080")
client.config is a live view: assign at any depth and the next fetch uses it. Launch-only fields (concurrency, chrome options) raise ValueError instead of failing silently. Full field list with docs: python/onyxweb/config.py.
Two knobs worth knowing, both off by default, since outerHTML drops this content:
onyxweb.Client(include_shadow_dom=True) # web components
onyxweb.Client(include_iframes=True) # same-origin iframes
Errors
try:
r = client.fetch(url)
except TimeoutError: # navigation + CDP timeouts
...
except onyxweb.OnyxwebError: # subclasses RuntimeError; carries .url and .kind
...
Development
uv sync # venv, deps, Rust extension in editable mode
uv run onyxweb-download-chrome
uv run pytest # tests are Python end-to-end; no Rust unit tests, on purpose
uv run pytest -m real_sites # integration tests against live sites (opt-in)
Editing src/*.rs rebuilds on the next uv run. Set ONYXWEB_LOG=debug for engine logs. Benchmarks and the engine comparison that led here are in BENCHMARKS.md.
License
BSD 3-Clause. The bundled chrome-headless-shell is also BSD-3-Clause (Google's Chrome for Testing).
Release files for onyxweb 0.2.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| onyxweb-0.2.3.tar.gz | 275.1 kB | Details |
Built distributions (wheels)
Total release size: 65.6 MB
Release files / onyxweb-0.2.3.tar.gz
| Download URL | onyxweb-0.2.3.tar.gz |
|---|---|
| Size | 275.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ef96df426f6f87c6fb256f7814f76c292f98747796151880c95662052b30274b
|
|
BLAKE2b-256 checksum How to use checksums |
1184cb15d45581326a99dd19ea4f21308cb0cda141cf489fa8eea0dffdd8b42c
|
| 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 Sep 19, 2026.
Transparency logRelease files / onyxweb-0.2.3-cp314-cp314-win_amd64.whl
| Download URL | onyxweb-0.2.3-cp314-cp314-win_amd64.whl |
|---|---|
| Size | 4.1 MB |
| Tags | CPython 3.14 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
52620095e98ba9780bb5c381757b4e8656b99ce3e9b6ee7e6bfe987da296e521
|
|
BLAKE2b-256 checksum How to use checksums |
093f2f560a49be8ce476e7d92871496cbc100888be3e6a2ae36fa82ecef26fe8
|
| 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 Sep 19, 2026.
Transparency logRelease files / onyxweb-0.2.3-cp314-cp314-macosx_11_0_arm64.whl
| Download URL | onyxweb-0.2.3-cp314-cp314-macosx_11_0_arm64.whl |
|---|---|
| Size | 3.6 MB |
| Tags | CPython 3.14 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
e55a94e291bb7e5cda9837337a41d69d9d7525b0af7dcdc6a49e624be349a208
|
|
BLAKE2b-256 checksum How to use checksums |
9ed67275fbde8959d20ff9b162dcf829a026c6ab326792d2db70bc6b09b201e8
|
| 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 Sep 19, 2026.
Transparency logRelease files / onyxweb-0.2.3-cp313-cp313-win_amd64.whl
| Download URL | onyxweb-0.2.3-cp313-cp313-win_amd64.whl |
|---|---|
| Size | 4.0 MB |
| Tags | CPython 3.13 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
e9ecb58eedcdfb2df3476d23dec3b1b533ade27437604af72ac5a8c548187805
|
|
BLAKE2b-256 checksum How to use checksums |
f9c1ac65370f48fe14b80681096b671e98364c92ff85d1b27683fa6e578f62f5
|
| 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 Sep 19, 2026.
Transparency logRelease files / onyxweb-0.2.3-cp313-cp313-manylinux_2_28_x86_64.whl
| Download URL | onyxweb-0.2.3-cp313-cp313-manylinux_2_28_x86_64.whl |
|---|---|
| Size | 3.9 MB |
| Tags | CPython 3.13 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
38f86981a646abce008399d8744c01dc508a20b34cd0fd171612628ae0e05618
|
|
BLAKE2b-256 checksum How to use checksums |
ccd919548a1417cbfa2457c75aea55cca7054c72249416023d41723cdb480654
|
| 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 Sep 19, 2026.
Transparency logRelease files / onyxweb-0.2.3-cp313-cp313-manylinux_2_28_aarch64.whl
| Download URL | onyxweb-0.2.3-cp313-cp313-manylinux_2_28_aarch64.whl |
|---|---|
| Size | 3.8 MB |
| Tags | CPython 3.13 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
a9442cf9c8825e949e8d8f558dcaddb1fa4e0f17142bd99325140d6d36db3446
|
|
BLAKE2b-256 checksum How to use checksums |
594f1f81d931f854da6ceeecda270dd03c889072336b1bad14c637ef5b26cc38
|
| 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 Sep 19, 2026.
Transparency logRelease files / onyxweb-0.2.3-cp313-cp313-macosx_11_0_arm64.whl
| Download URL | onyxweb-0.2.3-cp313-cp313-macosx_11_0_arm64.whl |
|---|---|
| Size | 3.6 MB |
| Tags | CPython 3.13 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
d55f0dcc5c2cd35be529576b0ddaadd7e643774dd144a2bc685876f829841ff1
|
|
BLAKE2b-256 checksum How to use checksums |
9c00d7b715427a10d709cd6a09de3297013608648079759071c7f3d52a23d289
|
| 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 Sep 19, 2026.
Transparency logRelease files / onyxweb-0.2.3-cp312-cp312-win_amd64.whl
| Download URL | onyxweb-0.2.3-cp312-cp312-win_amd64.whl |
|---|---|
| Size | 4.0 MB |
| Tags | CPython 3.12 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
6f3f2ba6087110ca93fc1ae45eb8e168ae5728365b1f4c3bc8135d7640b3c0eb
|
|
BLAKE2b-256 checksum How to use checksums |
de9a25433f5d9326d4ea3a7a4c64dc152e61f0602b57858a4e32daa2a8eb440a
|
| 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 Sep 19, 2026.
Transparency logRelease files / onyxweb-0.2.3-cp312-cp312-manylinux_2_28_x86_64.whl
| Download URL | onyxweb-0.2.3-cp312-cp312-manylinux_2_28_x86_64.whl |
|---|---|
| Size | 3.9 MB |
| Tags | CPython 3.12 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
57c2dae1f68805237ab7424bbbf89ddcabecf2f0a39204f9c4865e10898b21d5
|
|
BLAKE2b-256 checksum How to use checksums |
e719171c16476b14ea9b665068304d0387c18f042351bcf083ff50bd52cd9483
|
| 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 Sep 19, 2026.
Transparency logRelease files / onyxweb-0.2.3-cp312-cp312-manylinux_2_28_aarch64.whl
| Download URL | onyxweb-0.2.3-cp312-cp312-manylinux_2_28_aarch64.whl |
|---|---|
| Size | 3.8 MB |
| Tags | CPython 3.12 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
2eb57a90a402efbb8c5ab42784606ada7aba88b4194b88f37f630d9be10c93cc
|
|
BLAKE2b-256 checksum How to use checksums |
ab6a8030178a1fe569ea820926dad9652ed67941fa49a60eb13be0f8a0ebf843
|
| 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 Sep 19, 2026.
Transparency logRelease files / onyxweb-0.2.3-cp312-cp312-macosx_11_0_arm64.whl
| Download URL | onyxweb-0.2.3-cp312-cp312-macosx_11_0_arm64.whl |
|---|---|
| Size | 3.6 MB |
| Tags | CPython 3.12 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
fd59a781c2358efbd474d4116e341d9714ec44685da6b9fc8f1ff5c8c9d18ba7
|
|
BLAKE2b-256 checksum How to use checksums |
78b250d12a054a19387ff46239685bd3d91844f75d480ecf631eeb39f3385ca8
|
| 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 Sep 19, 2026.
Transparency logRelease files / onyxweb-0.2.3-cp311-cp311-win_amd64.whl
| Download URL | onyxweb-0.2.3-cp311-cp311-win_amd64.whl |
|---|---|
| Size | 4.0 MB |
| Tags | CPython 3.11 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
cb1db1248dcb92078bc645dd2f0b71c79ccec11353452d1576ab040981a57128
|
|
BLAKE2b-256 checksum How to use checksums |
a09020c81d8454179a302dc3426f07fbb5f5af69c1f5ad19b38d9d7ce9d9f103
|
| 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 Sep 19, 2026.
Transparency logRelease files / onyxweb-0.2.3-cp311-cp311-manylinux_2_28_x86_64.whl
| Download URL | onyxweb-0.2.3-cp311-cp311-manylinux_2_28_x86_64.whl |
|---|---|
| Size | 3.9 MB |
| Tags | CPython 3.11 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
56154c5443d4bcbe431c8b488486eec46b2a5cc7d1febb677181d0107324b091
|
|
BLAKE2b-256 checksum How to use checksums |
dc60fb5e1e77eb5957709b7726f118137d5030384e774d207f0b308219ed58dd
|
| 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 Sep 19, 2026.
Transparency logRelease files / onyxweb-0.2.3-cp311-cp311-manylinux_2_28_aarch64.whl
| Download URL | onyxweb-0.2.3-cp311-cp311-manylinux_2_28_aarch64.whl |
|---|---|
| Size | 3.8 MB |
| Tags | CPython 3.11 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
6dd59bf2f4a851ccd4e898e769501be98e8fc47eb50d22e82443915a3e4cdbe1
|
|
BLAKE2b-256 checksum How to use checksums |
d2d6913c9229241f882ffc92adb5cf5688118660dab537c0cb184d508c6bd4e8
|
| 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 Sep 19, 2026.
Transparency logRelease files / onyxweb-0.2.3-cp311-cp311-macosx_11_0_arm64.whl
| Download URL | onyxweb-0.2.3-cp311-cp311-macosx_11_0_arm64.whl |
|---|---|
| Size | 3.6 MB |
| Tags | CPython 3.11 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
421e6363af08b455eef81bddda52d2f8970b48692f39540515d9f67b76837f7a
|
|
BLAKE2b-256 checksum How to use checksums |
ea0b960e2fa70c102f75c7ac593657d57f33f4bc4503b8d6aea89368d99f74d0
|
| 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 Sep 19, 2026.
Transparency logRelease files / onyxweb-0.2.3-cp310-cp310-win_amd64.whl
| Download URL | onyxweb-0.2.3-cp310-cp310-win_amd64.whl |
|---|---|
| Size | 4.0 MB |
| Tags | CPython 3.10 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
36b39063f3f0e2fa592a067c46e57a1beae9f6527c067f9f77eaeb877d8135e2
|
|
BLAKE2b-256 checksum How to use checksums |
c56eebcdb2b40e21812b48f4a5dadc0f302c41500f61f52d8c2466234089ed0f
|
| 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 Sep 19, 2026.
Transparency logRelease files / onyxweb-0.2.3-cp310-cp310-manylinux_2_28_x86_64.whl
| Download URL | onyxweb-0.2.3-cp310-cp310-manylinux_2_28_x86_64.whl |
|---|---|
| Size | 3.9 MB |
| Tags | CPython 3.10 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
e673efa611420babe63dc42b641593d65067172c82032f631be078e6af218313
|
|
BLAKE2b-256 checksum How to use checksums |
d2750eff77baec9a2c34820affae6236746358760a61f63cda6cca5423baa0a8
|
| 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 Sep 19, 2026.
Transparency logRelease files / onyxweb-0.2.3-cp310-cp310-manylinux_2_28_aarch64.whl
| Download URL | onyxweb-0.2.3-cp310-cp310-manylinux_2_28_aarch64.whl |
|---|---|
| Size | 3.8 MB |
| Tags | CPython 3.10 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
fae6bec0ba5a7d7330ef470a8740a903d0cb23d0c9728b67f4eb7cf6c97edea7
|
|
BLAKE2b-256 checksum How to use checksums |
37f91fdb4ac87c3e559228c8c56a98c5fd08203d321bf62cef9f1a0cbf72ae1f
|
| 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 Sep 19, 2026.
Transparency log