Skip to main content
Pre-release

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

cybrentq

A production-quality Cython implementation of Brent's root-finding method. The algorithm is a faithful translation of the C routine in scipy/optimize/Zeros/brentq.c: bisection guarded by inverse quadratic interpolation, with a secant fallback and bisection used whenever an interpolation step would not make adequate progress.

The public API mirrors the relevant subset of scipy.optimize.brentq and can serve as a drop-in replacement in most code paths.

Requires Python 3.10 or newer and a working C compiler (used during install to compile the Cython extension).

Quick start

This project uses uv for environment and dependency management, with a Makefile wrapping the most common commands.

# Install uv if you don't have it:
#   curl -LsSf https://astral.sh/uv/install.sh | sh   (macOS / Linux)
#   powershell -c "irm https://astral.sh/uv/install.ps1 | iex"   (Windows)

# Recommended: use the Makefile. PYTHON_VERSION=3.10 by default.
# The Cython extension is compiled during `make sync`.
make venv
make sync

The Makefile passes hardening flags the bare commands omit (--frozen --refresh --all-extras --all-groups --link-mode=copy, plus --seed --prompt=cybrentq on venv). Read the Makefile for the full invocations.

If you want a minimal install without the Makefile:

uv venv --python 3.10       # create the venv
uv sync                     # install project + default groups, compile Cython
uv sync --only-group test   # install just the test group, nothing else
uv sync --no-dev            # consumer-style install (no dev groups)

uv sync reads pyproject.toml, provisions a matching interpreter, builds the C extension via the PEP 517 backend (setuptools + Cython), and writes a uv.lock. Commit uv.lock for reproducible builds across machines.

Editable iteration on the Cython source

uv sync installs the project into the managed venv. After editing _brentq.pyx, re-run uv sync --reinstall-package cybrentq (or just uv sync if you also bump the version) to force a recompile.

Usage

import math
from cybrentq import brentq

# Basic usage — finds sqrt(2)
root = brentq(lambda x: x * x - 2.0, 0.0, 2.0)

# Pass extra arguments via the args tuple
root = brentq(lambda x, target: x ** 3 - target, 0.0, 5.0, args=(27.0,))

# Diagnostics
root, info = brentq(lambda x: math.cos(x) - x, 0.0, 1.0, full_output=True)
print(info)
# RootResults(root=0.7390851332151559, iterations=7, function_calls=8,
#             converged=True, flag='converged')

Signature

brentq(
    f,                          # callable, f(x, *args) -> float
    a, b,                       # bracketing interval, f(a)*f(b) < 0
    args=(),                    # extra positional args forwarded to f
    xtol=2e-12,                 # absolute tolerance
    rtol=4*eps,                 # relative tolerance (>= 4 * machine eps)
    maxiter=100,                # iteration budget
    full_output=False,          # return RootResults alongside the root
    disp=True,                  # raise on non-convergence instead of returning a flag
) -> float | tuple[float, RootResults]

The return type depends on full_output, so _brentq.pyi splits it into two overloads keyed on Literal[True] / Literal[False]. Pass full_output=True as a keyword argument — the runtime accepts it positionally, but the stub only declares the keyword form, so a type checker rejects the positional one.

Errors

Condition Behaviour
f(a) and f(b) have the same sign ValueError
xtol <= 0, rtol < 4*eps, or maxiter < 1 ValueError
Iteration budget exhausted and disp=True ConvergenceError
Iteration budget exhausted and disp=False returns the last iterate: (root, RootResults(converged=False, flag='convergence error')) with full_output=True, otherwise the bare root
User-supplied f raises exception propagates unchanged

Tests

make test                                   # all tests
make cov                                    # coverage run (see warning below)
make report                                 # print coverage report from last run

# Direct equivalents for `make test`:
uv run pytest                               # all tests
uv run pytest tests/test_basic.py           # just behaviour / error tests
uv run pytest tests/test_against_scipy.py   # head-to-head correctness vs scipy
uv run pytest tests/test_performance.py     # perf regression guard (CI-safe)

Every supported Python at once

noxfile.py drives pytest against 3.10 – 3.14, using uv as the venv backend:

uvx nox                  # default session, every supported Python
uvx nox -s tests-3.12    # a single version
uvx nox -- -k brentq     # forward args to pytest

Smoke test

scripts/smoke.py imports the installed package, solves for √2 and asserts the result. It is deliberately a plain script with a module-level assert rather than a pytest test, because cibuildwheel runs it as python scripts/smoke.py inside each freshly built wheel's environment, where the dev dependencies do not exist.

make smoke               # uv run --frozen python scripts/smoke.py

Note on make cov: the target wipes .c/.so artifacts and reinstalls cybrentq with CYTHON_TRACE=1 so that coverage.py (via the Cython.Coverage plugin) can report line coverage from _brentq.pyx. The traced build is significantly slower at runtime. After running make cov, run make sync before make bench — otherwise the traced extension will skew benchmark numbers.

The scipy-comparison suite asserts that:

  • both implementations report converged=True on every problem,
  • root estimates agree to within 1e-10 relative and absolute tolerance,
  • iteration counts and function-call counts match exactly (Brent's method is deterministic, so any divergence flags a bug in our translation).

Benchmarks

The benchmark suite compares this Cython brentq against scipy.optimize.brentq and against pymodab (a C implementation of the Modified Anderson-Björck root-finding method) across nine problems.

make bench                                              # default config
make bench BENCH_ARGS="--n-calls 5000 --repeats 7"      # override args

# Direct equivalent:
uv run python benchmarks/bench_brentq.py --n-calls 5000 --repeats 7

Sample output (numbers depend on the machine, Python build, and library versions):

problem                            scipy (µs)  cython (µs)   modab (µs)    cy/sc    mb/sc
-----------------------------------------------------------------------------------------
x^2 - 2 (cheap)                         8.374        0.518        2.665   16.16x    3.14x
x^3 - x - 2 (cheap)                     8.957        0.875        2.925   10.24x    3.06x
cos(x) - x                              7.978        0.782        2.718   10.20x    2.94x
exp(x) - 2                              9.862        0.981        2.950   10.05x    3.34x
sin(x), root at pi                      6.623        0.287        2.210   23.04x    3.00x
(x-1)^3 (flat)                          3.566        0.257        1.770   13.90x    2.02x
atan(1000*(x-0.5)) (steep)              3.692        0.341        1.864   10.82x    1.98x
poly degree 5                          13.879        2.010        4.445    6.90x    3.12x
expensive f (sum of 50 sines)          69.151       57.117       59.970    1.21x    1.15x
-----------------------------------------------------------------------------------------
cython vs scipy: gmean 9.24x  min 1.21x  max 23.04x
modab  vs scipy: gmean 2.52x  min 1.15x  max 3.34x

Columns: cy/sc is scipy_time / cython_time (Cython speedup over scipy); mb/sc is scipy_time / modab_time (pymodab speedup over scipy). Higher is better in both columns.

Before each timed problem the runner calls all three implementations and asserts the roots agree to within 1e-9 — a benchmark with a silent correctness regression is worse than one that doesn't run.

A few things to note when reading the numbers:

  • Brent's method usually converges in 6–15 iterations, so most of the wall time of a single solve is spent inside f, not inside the algorithm. When f is expensive (the "sum of 50 sines" row), all implementations spend the vast majority of their time in f and look nearly identical.
  • The Cython win is largest when f is cheap, because that is when the algorithm's own overhead matters most.
  • pymodab's Modified Anderson-Björck typically uses fewer f evaluations than Brent — but each iteration carries pure-Python wrapper overhead here, so it lands between scipy and our Cython version.

Building distributions

make build            # equivalent to: uv build
                      # produces sdist + wheel under dist/

Make targets

make help lists every target with a short description.

Target Action
venv Create the project venv via uv venv (PYTHON_VERSION=3.10 by default)
lock Resolve and write uv.lock (uv lock --upgrade --resolution=highest --refresh)
outdated Show outdated direct and transitive deps
sync Sync the venv with uv.lock (all groups + extras)
test Run the test suite without coverage
cov / test/cov Recompile extension with CYTHON_TRACE=1 and run under coverage.py (no pytest-cov). Run make sync afterward to restore the fast build.
report / cov/report Print the coverage report from the last make cov
bench Run the benchmark suite (override args via BENCH_ARGS=…)
smoke Import-and-solve smoke test against the installed package
lint / lint/check Read-only ruff check
lint/fix Rewrites filesruff check --fix
fmt / fmt/check Read-only ruff format --check
fmt/fix Rewrites filesruff format
typecheck Read-only pyrefly check over the project
check lint/check + fmt/check + typecheck (CI-safe)
build / dist Build sdist + wheel into dist/
clean Remove build artifacts and coverage data

Bare lint and fmt are intentionally read-only; mutation requires the explicit /fix variant so typos don't rewrite the tree.

Linting and formatting

The project pins ruff (configuration in pyproject.toml under [tool.ruff]). Enabled rule families:

Code Family
E / W pycodestyle errors / warnings
F pyflakes (unused imports, undefined names)
I isort
N pep8-naming
UP pyupgrade
C90 mccabe complexity (max-complexity = 10)
A flake8-builtins (shadowing)
B flake8-bugbear
PERF perflint
PT flake8-pytest-style
RUF ruff-native rules
SIM flake8-simplify
TRY tryceratops (exception hygiene)

Ruff lints .py files only — _brentq.pyx is outside the ruff scope.

make check            # lint + format + type check, no mutations (use this in CI)
make lint/fix         # rewrites files: ruff check --fix
make fmt/fix          # rewrites files: ruff format

Type checking

The project pins pyrefly (configuration in pyproject.toml under [tool.pyrefly]) on the strict preset, with python-version = "3.10" so results do not drift with whichever interpreter the venv happens to hold.

make typecheck        # uv run --frozen pyrefly check

Two deliberate relaxations:

  • tests/** disables implicit-any-parameter and implicit-any-lambda. brentq takes Callable[..., float] (it has to — args is forwarded to f), so the bare lambdas the tests pass in cannot have inferable parameter types. Every other strict check still applies to tests.
  • setup.py is excluded: a build script, not shipped code.

Like ruff, pyrefly does not read _brentq.pyx. The type contract for the extension lives entirely in _brentq.pyi, so a change to the .pyx signature has to be mirrored there by hand.

Pre-commit hooks

.pre-commit-config.yaml runs the pre-commit-hooks basics, ruff check, ruff format and pyrefly. CI enforces the same set via prek, so installing the hooks locally is the cheapest way to avoid a red lint job:

uvx prek install              # or: uv run pre-commit install
uvx prek run --all-files      # run everything now

The pyrefly hook is a repo: local hook that shells out to uv run --frozen pyrefly check, so the version that runs is always the one in uv.lock — there is no second pin to keep in sync.

Layout

src/cybrentq/
  _brentq.pyx           # the algorithm
  _brentq.pyi           # type stubs for IDEs and pyrefly
  __init__.py           # re-exports brentq, RootResults, ConvergenceError
  py.typed              # PEP 561 marker
tests/
  conftest.py           # shared fixture: 11 canonical root-finding problems
  test_basic.py         # behaviour, error paths, edge cases
  test_against_scipy.py # parity vs scipy
  test_performance.py   # perf regression guard
benchmarks/
  bench_brentq.py       # speed comparison vs scipy and pymodab
scripts/
  smoke.py              # import-and-solve check, also run by cibuildwheel
setup.py                # Extension + cythonize; the PEP 517 backend calls it
noxfile.py              # pytest across Python 3.10 - 3.14 via `uvx nox`
Makefile                # venv, sync, test, cov, bench, lint, fmt, typecheck, build
pyproject.toml          # project metadata + ruff/pyrefly/coverage/pytest config
.pre-commit-config.yaml # hooks, enforced in CI via prek

License

MIT — see LICENSE.

Release files for cybrentq 0.1.4rc5

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

Source distribution (sdist)

Source distribution for cybrentq 0.1.4rc5
File Size Uploaded
cybrentq-0.1.4rc5.tar.gz 146.4 kB Details

Built distributions (wheels)

Table of built distributions (wheels) for cybrentq 0.1.4rc5
File
cybrentq-0.1.4rc5-cp314-cp314-win_amd64.whl CPython 3.14 CPython 3.14 Windows x86-64 Details
cybrentq-0.1.4rc5-cp314-cp314-musllinux_1_2_x86_64.whl CPython 3.14 CPython 3.14 Linux musl 1.2+ x86-64 Details
cybrentq-0.1.4rc5-cp314-cp314-musllinux_1_2_aarch64.whl CPython 3.14 CPython 3.14 Linux musl 1.2+ ARM64 Details
cybrentq-0.1.4rc5-cp314-cp314-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl CPython 3.14 CPython 3.14 Linux glibc 2.28+ x86-64, Linux glibc 2.17+ x86-64 Details
cybrentq-0.1.4rc5-cp314-cp314-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl CPython 3.14 CPython 3.14 Linux glibc 2.17+ ARM64, Linux glibc 2.28+ ARM64 Details
cybrentq-0.1.4rc5-cp314-cp314-macosx_11_0_arm64.whl CPython 3.14 CPython 3.14 macOS 11.0+ ARM64 Details
cybrentq-0.1.4rc5-cp313-cp313-win_amd64.whl CPython 3.13 CPython 3.13 Windows x86-64 Details
cybrentq-0.1.4rc5-cp313-cp313-musllinux_1_2_x86_64.whl CPython 3.13 CPython 3.13 Linux musl 1.2+ x86-64 Details
cybrentq-0.1.4rc5-cp313-cp313-musllinux_1_2_aarch64.whl CPython 3.13 CPython 3.13 Linux musl 1.2+ ARM64 Details
cybrentq-0.1.4rc5-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl CPython 3.13 CPython 3.13 Linux glibc 2.17+ x86-64, Linux glibc 2.28+ x86-64 Details
cybrentq-0.1.4rc5-cp313-cp313-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl CPython 3.13 CPython 3.13 Linux glibc 2.17+ ARM64, Linux glibc 2.28+ ARM64 Details
cybrentq-0.1.4rc5-cp313-cp313-macosx_11_0_arm64.whl CPython 3.13 CPython 3.13 macOS 11.0+ ARM64 Details
cybrentq-0.1.4rc5-cp312-cp312-win_amd64.whl CPython 3.12 CPython 3.12 Windows x86-64 Details
cybrentq-0.1.4rc5-cp312-cp312-musllinux_1_2_x86_64.whl CPython 3.12 CPython 3.12 Linux musl 1.2+ x86-64 Details
cybrentq-0.1.4rc5-cp312-cp312-musllinux_1_2_aarch64.whl CPython 3.12 CPython 3.12 Linux musl 1.2+ ARM64 Details
cybrentq-0.1.4rc5-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl CPython 3.12 CPython 3.12 Linux glibc 2.28+ x86-64, Linux glibc 2.17+ x86-64 Details
cybrentq-0.1.4rc5-cp312-cp312-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl CPython 3.12 CPython 3.12 Linux glibc 2.17+ ARM64, Linux glibc 2.28+ ARM64 Details
cybrentq-0.1.4rc5-cp312-cp312-macosx_11_0_arm64.whl CPython 3.12 CPython 3.12 macOS 11.0+ ARM64 Details
cybrentq-0.1.4rc5-cp311-cp311-win_amd64.whl CPython 3.11 CPython 3.11 Windows x86-64 Details
cybrentq-0.1.4rc5-cp311-cp311-musllinux_1_2_x86_64.whl CPython 3.11 CPython 3.11 Linux musl 1.2+ x86-64 Details
cybrentq-0.1.4rc5-cp311-cp311-musllinux_1_2_aarch64.whl CPython 3.11 CPython 3.11 Linux musl 1.2+ ARM64 Details
cybrentq-0.1.4rc5-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl CPython 3.11 CPython 3.11 Linux glibc 2.28+ x86-64, Linux glibc 2.17+ x86-64 Details
cybrentq-0.1.4rc5-cp311-cp311-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl CPython 3.11 CPython 3.11 Linux glibc 2.17+ ARM64, Linux glibc 2.28+ ARM64 Details
cybrentq-0.1.4rc5-cp311-cp311-macosx_11_0_arm64.whl CPython 3.11 CPython 3.11 macOS 11.0+ ARM64 Details
cybrentq-0.1.4rc5-cp310-cp310-win_amd64.whl CPython 3.10 CPython 3.10 Windows x86-64 Details
cybrentq-0.1.4rc5-cp310-cp310-musllinux_1_2_x86_64.whl CPython 3.10 CPython 3.10 Linux musl 1.2+ x86-64 Details
cybrentq-0.1.4rc5-cp310-cp310-musllinux_1_2_aarch64.whl CPython 3.10 CPython 3.10 Linux musl 1.2+ ARM64 Details
cybrentq-0.1.4rc5-cp310-cp310-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl CPython 3.10 CPython 3.10 Linux glibc 2.17+ x86-64, Linux glibc 2.28+ x86-64 Details
cybrentq-0.1.4rc5-cp310-cp310-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl CPython 3.10 CPython 3.10 Linux glibc 2.17+ ARM64, Linux glibc 2.28+ ARM64 Details
cybrentq-0.1.4rc5-cp310-cp310-macosx_11_0_arm64.whl CPython 3.10 CPython 3.10 macOS 11.0+ ARM64 Details

Total release size: 5.4 MB

Release files / cybrentq-0.1.4rc5.tar.gz

Download URL cybrentq-0.1.4rc5.tar.gz
Size 146.4 kB
Tags Source
SHA-256 checksum
How to use checksums
205732f458016c0b10a5d1b7be58db72b99a49698bde5d972cb6ba90a279642e
BLAKE2b-256 checksum
How to use checksums
7882ec4a237de5ffda1e706425441a011ed935f1ffd251484305603a7e8ef2fa
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.13

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 Aug 13, 2026.

Transparency log

Release files / cybrentq-0.1.4rc5-cp314-cp314-win_amd64.whl

Download URL cybrentq-0.1.4rc5-cp314-cp314-win_amd64.whl
Size 35.9 kB
Tags CPython 3.14 Windows x86-64
SHA-256 checksum
How to use checksums
8dd4652f3406e069dc2ec674757011189d88c4188731d0a8cb3b4f7ed2b78639
BLAKE2b-256 checksum
How to use checksums
093b30533aaa02af93b05d0c1a6e66ffe6bb1af343e0fce2f175311ab402b775
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.13

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 Aug 13, 2026.

Transparency log

Release files / cybrentq-0.1.4rc5-cp314-cp314-musllinux_1_2_x86_64.whl

Download URL cybrentq-0.1.4rc5-cp314-cp314-musllinux_1_2_x86_64.whl
Size 231.8 kB
Tags CPython 3.14 Linux musl 1.2+ x86-64
SHA-256 checksum
How to use checksums
611ee9675a1e2a8dae225e7b15292325336833a4c25d4039a079022612cbbda8
BLAKE2b-256 checksum
How to use checksums
284a2fe16d03770c6e1453d9dd74db98c6ce9d64780e27d9ad0ff949dceec2a8
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.13

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 Aug 13, 2026.

Transparency log

Release files / cybrentq-0.1.4rc5-cp314-cp314-musllinux_1_2_aarch64.whl

Download URL cybrentq-0.1.4rc5-cp314-cp314-musllinux_1_2_aarch64.whl
Size 223.8 kB
Tags CPython 3.14 Linux musl 1.2+ ARM64
SHA-256 checksum
How to use checksums
7b8b83b520f63835b9ebb9a21b34ef0987f540c2791721d9102811037f71e00c
BLAKE2b-256 checksum
How to use checksums
17f40fa668ec3e070bf51fc6c94d400dcb29d09fd2e67ce10b5159aad4a36251
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.13

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 Aug 13, 2026.

Transparency log

Release files / cybrentq-0.1.4rc5-cp314-cp314-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl

Download URL cybrentq-0.1.4rc5-cp314-cp314-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Size 232.6 kB
Tags CPython 3.14 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
4e3ccd70df9b28c9653428207dade2d864cb33e859e2a8cb8a217db976b101b9
BLAKE2b-256 checksum
How to use checksums
f70701c8b5b1ddf84cc21f4cf21198509bd715ea454ab96d16604a0771a9853e
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.13

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 Aug 13, 2026.

Transparency log

Release files / cybrentq-0.1.4rc5-cp314-cp314-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl

Download URL cybrentq-0.1.4rc5-cp314-cp314-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
Size 227.8 kB
Tags CPython 3.14 Linux glibc 2.17+ ARM64 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
f2240e8d62157a9204353f3f14be72bc0a81fcfa92a91e39b66b2defefadd899
BLAKE2b-256 checksum
How to use checksums
66810e6ac9b5392008629d798cf3bcc1932d3acb96a775b9ff86bd97086a90b4
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.13

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 Aug 13, 2026.

Transparency log

Release files / cybrentq-0.1.4rc5-cp314-cp314-macosx_11_0_arm64.whl

Download URL cybrentq-0.1.4rc5-cp314-cp314-macosx_11_0_arm64.whl
Size 107.4 kB
Tags CPython 3.14 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
a672d012558667167e297040804ae4624f6891758a80d417fece5c7e442f682e
BLAKE2b-256 checksum
How to use checksums
f6642bb759c5f60c941b64790af7a1be531e9e68198226c853466361dce77ac9
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.13

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 Aug 13, 2026.

Transparency log

Release files / cybrentq-0.1.4rc5-cp313-cp313-win_amd64.whl

Download URL cybrentq-0.1.4rc5-cp313-cp313-win_amd64.whl
Size 35.2 kB
Tags CPython 3.13 Windows x86-64
SHA-256 checksum
How to use checksums
52500ad0f317e261624a073a97f1d15e254bc61f920b706fe773110fb3ba5245
BLAKE2b-256 checksum
How to use checksums
4711f48db446684c07c7bb37b8e7c521d8559d2fe99d2b592680197de2778f25
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.13

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 Aug 13, 2026.

Transparency log

Release files / cybrentq-0.1.4rc5-cp313-cp313-musllinux_1_2_x86_64.whl

Download URL cybrentq-0.1.4rc5-cp313-cp313-musllinux_1_2_x86_64.whl
Size 233.1 kB
Tags CPython 3.13 Linux musl 1.2+ x86-64
SHA-256 checksum
How to use checksums
ede6307739717280e5b03033e538fa4658ecfefe188deb8d5b99b49a9828ec53
BLAKE2b-256 checksum
How to use checksums
038682f90990dbe87c48cdf431f0e3d3a71dc969d114d604845a2d7e94eb165c
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.13

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 Aug 13, 2026.

Transparency log

Release files / cybrentq-0.1.4rc5-cp313-cp313-musllinux_1_2_aarch64.whl

Download URL cybrentq-0.1.4rc5-cp313-cp313-musllinux_1_2_aarch64.whl
Size 224.6 kB
Tags CPython 3.13 Linux musl 1.2+ ARM64
SHA-256 checksum
How to use checksums
8f91d2c374a24c996aab20e8ab0ad230b5bc2ab9ca71403221b871649720bf20
BLAKE2b-256 checksum
How to use checksums
4470035c2055d993705303e4b381fb65a528b155db5c41aaa6d9cbe205b5686c
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.13

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 Aug 13, 2026.

Transparency log

Release files / cybrentq-0.1.4rc5-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl

Download URL cybrentq-0.1.4rc5-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Size 232.9 kB
Tags CPython 3.13 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
4601c80e8ae819f56b253c9d10b21b28b0e7b87b02a155b22c5fd015dac86454
BLAKE2b-256 checksum
How to use checksums
aee4a97046735634cda58ac4e32c76aeeaf4a2c0d071acd052d0317259761f6f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.13

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 Aug 13, 2026.

Transparency log

Release files / cybrentq-0.1.4rc5-cp313-cp313-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl

Download URL cybrentq-0.1.4rc5-cp313-cp313-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
Size 227.7 kB
Tags CPython 3.13 Linux glibc 2.17+ ARM64 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
9e9b9b1a12bc5280e9398b515f226f001ff96c827c51335056a22276de3a509e
BLAKE2b-256 checksum
How to use checksums
b4b12e6e74c0443b91f581c1d45601e5d774ae412ed151f5bf56dc30918bcfd8
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.13

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 Aug 13, 2026.

Transparency log

Release files / cybrentq-0.1.4rc5-cp313-cp313-macosx_11_0_arm64.whl

Download URL cybrentq-0.1.4rc5-cp313-cp313-macosx_11_0_arm64.whl
Size 106.3 kB
Tags CPython 3.13 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
b89f79f40fa59b135fcc93fade009038d530a3628333d5772fb813103937a651
BLAKE2b-256 checksum
How to use checksums
fa9083c3bbc2c5286ebdfe2af180d3d71c79d27d2d63df89791d7e73d2795190
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.13

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 Aug 13, 2026.

Transparency log

Release files / cybrentq-0.1.4rc5-cp312-cp312-win_amd64.whl

Download URL cybrentq-0.1.4rc5-cp312-cp312-win_amd64.whl
Size 36.1 kB
Tags CPython 3.12 Windows x86-64
SHA-256 checksum
How to use checksums
5adac7521ef0cf9a40274e9943eb67e624e7e818a6f1cf233879ba64decff151
BLAKE2b-256 checksum
How to use checksums
af48c4b6adde9342b676f88cdf6a8ffebbe65c1d7ca15caab83fb76cfd1244ee
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.13

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 Aug 13, 2026.

Transparency log

Release files / cybrentq-0.1.4rc5-cp312-cp312-musllinux_1_2_x86_64.whl

Download URL cybrentq-0.1.4rc5-cp312-cp312-musllinux_1_2_x86_64.whl
Size 236.8 kB
Tags CPython 3.12 Linux musl 1.2+ x86-64
SHA-256 checksum
How to use checksums
925590805229c5b2f8aa4350ee1651a94fed59d556ae4a0a0516e44c2578f08c
BLAKE2b-256 checksum
How to use checksums
ca0eb9378635bb94b596c2fb9c685bccef0f3c7eb59d5367699f878f3912305e
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.13

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 Aug 13, 2026.

Transparency log

Release files / cybrentq-0.1.4rc5-cp312-cp312-musllinux_1_2_aarch64.whl

Download URL cybrentq-0.1.4rc5-cp312-cp312-musllinux_1_2_aarch64.whl
Size 229.2 kB
Tags CPython 3.12 Linux musl 1.2+ ARM64
SHA-256 checksum
How to use checksums
acd355c667d7c2f03ca4b21692865f2aba47279662ca5631352292f067e3346e
BLAKE2b-256 checksum
How to use checksums
2acd5f16dc7c7445f8b66cd3b369d1753a4d0be0301011a1d6215312c2f8f246
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.13

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 Aug 13, 2026.

Transparency log

Release files / cybrentq-0.1.4rc5-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl

Download URL cybrentq-0.1.4rc5-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Size 237.1 kB
Tags CPython 3.12 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
be20a3c4c8a015abce6a5302946e0b8dfefe92a986558e7ef3ce761c10d3b8d6
BLAKE2b-256 checksum
How to use checksums
2dc1bf1c517377e080428f7f82be4ee542e6e781ebd62dc05d82b8d33d6fa790
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.13

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 Aug 13, 2026.

Transparency log

Release files / cybrentq-0.1.4rc5-cp312-cp312-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl

Download URL cybrentq-0.1.4rc5-cp312-cp312-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
Size 231.7 kB
Tags CPython 3.12 Linux glibc 2.17+ ARM64 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
d3699a85bd1bb05ba441ea2d329c770fec634fef440a463fdea11df2e82e5a8e
BLAKE2b-256 checksum
How to use checksums
02500632a06f1724e7e4ffc407987a93222261e9151f1b33e5e6a1b4c1419368
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.13

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 Aug 13, 2026.

Transparency log

Release files / cybrentq-0.1.4rc5-cp312-cp312-macosx_11_0_arm64.whl

Download URL cybrentq-0.1.4rc5-cp312-cp312-macosx_11_0_arm64.whl
Size 107.1 kB
Tags CPython 3.12 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
07782e5fa4a8af517bf8607148714fb346a09a38410ae07fff45e5bc11be88c6
BLAKE2b-256 checksum
How to use checksums
96046713583e9e3e79e44cf0ab6a14d0a22286f6a05d51a2d341f46338d7003c
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.13

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 Aug 13, 2026.

Transparency log

Release files / cybrentq-0.1.4rc5-cp311-cp311-win_amd64.whl

Download URL cybrentq-0.1.4rc5-cp311-cp311-win_amd64.whl
Size 35.7 kB
Tags CPython 3.11 Windows x86-64
SHA-256 checksum
How to use checksums
5c811592cfae25feb62d18997cea2c191bd8c09bcb6227735f622c7ea3a6b30d
BLAKE2b-256 checksum
How to use checksums
0392297b50637ec438c8fe4f27eb01c2a0c72df9248ce5fb5da61d178b600467
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.13

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 Aug 13, 2026.

Transparency log

Release files / cybrentq-0.1.4rc5-cp311-cp311-musllinux_1_2_x86_64.whl

Download URL cybrentq-0.1.4rc5-cp311-cp311-musllinux_1_2_x86_64.whl
Size 233.7 kB
Tags CPython 3.11 Linux musl 1.2+ x86-64
SHA-256 checksum
How to use checksums
9958d8dd3ab62b8d42a7934c0c696945821fb260be3a87c86773c81cb8e42ef3
BLAKE2b-256 checksum
How to use checksums
310bc48490066f5ab7c0761bdb04fe7c43bf21dbd39c15ff91090d0e0a34d395
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.13

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 Aug 13, 2026.

Transparency log

Release files / cybrentq-0.1.4rc5-cp311-cp311-musllinux_1_2_aarch64.whl

Download URL cybrentq-0.1.4rc5-cp311-cp311-musllinux_1_2_aarch64.whl
Size 226.9 kB
Tags CPython 3.11 Linux musl 1.2+ ARM64
SHA-256 checksum
How to use checksums
ab83d3ae64ba7f068d98d82ad8d9a836b9a21496342d61d4155865f902e970c3
BLAKE2b-256 checksum
How to use checksums
f14d5817a48c8f1dc7156b36638f0e611cb35999bebd1967b79fc8bfb5ae2e68
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.13

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 Aug 13, 2026.

Transparency log

Release files / cybrentq-0.1.4rc5-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl

Download URL cybrentq-0.1.4rc5-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Size 233.0 kB
Tags CPython 3.11 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
5a0c8cb1c42b218abab14dbbde4209f471e80f5a09af27e9a590a48b5b95f551
BLAKE2b-256 checksum
How to use checksums
d8f32a8b38490b74bc8022c7ea9cba0ee380ae094b83cac4fa953dbb8e4a9b51
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.13

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 Aug 13, 2026.

Transparency log

Release files / cybrentq-0.1.4rc5-cp311-cp311-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl

Download URL cybrentq-0.1.4rc5-cp311-cp311-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
Size 229.0 kB
Tags CPython 3.11 Linux glibc 2.17+ ARM64 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
3d46838f0261a2c40ade05dc9019a60af18c13333cdd11f6baabb441c764c8dc
BLAKE2b-256 checksum
How to use checksums
898e9e24688fef436d3b51dbfd1944808dba73f83fcd48b0c3147a3ad4927baa
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.13

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 Aug 13, 2026.

Transparency log

Release files / cybrentq-0.1.4rc5-cp311-cp311-macosx_11_0_arm64.whl

Download URL cybrentq-0.1.4rc5-cp311-cp311-macosx_11_0_arm64.whl
Size 107.4 kB
Tags CPython 3.11 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
d1c512c5cf8c166f754e2a18276581b9e152bb3db6000e1faaa2b852542b1643
BLAKE2b-256 checksum
How to use checksums
521a482df97fe5235d511ac80bb4a6deeabfe6727a37047d87f30f060deac5ca
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.13

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 Aug 13, 2026.

Transparency log

Release files / cybrentq-0.1.4rc5-cp310-cp310-win_amd64.whl

Download URL cybrentq-0.1.4rc5-cp310-cp310-win_amd64.whl
Size 35.9 kB
Tags CPython 3.10 Windows x86-64
SHA-256 checksum
How to use checksums
f2004feffe80b14bac79eeb20cab73e78fe67ffc62e013032055c71413a925fa
BLAKE2b-256 checksum
How to use checksums
cab6dc6336457149a20ca1c7e0aed3557e5629e744d3b56ab06f2f824964befa
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.13

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 Aug 13, 2026.

Transparency log

Release files / cybrentq-0.1.4rc5-cp310-cp310-musllinux_1_2_x86_64.whl

Download URL cybrentq-0.1.4rc5-cp310-cp310-musllinux_1_2_x86_64.whl
Size 221.2 kB
Tags CPython 3.10 Linux musl 1.2+ x86-64
SHA-256 checksum
How to use checksums
df51de32082656af460911790de5e50a4120d98ebaee36f10473eb8a8f3a3e1d
BLAKE2b-256 checksum
How to use checksums
2002625d7d33fb5488eb1ea75fff96eafc434611efff4b0de55450e2eca0bcb7
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.13

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 Aug 13, 2026.

Transparency log

Release files / cybrentq-0.1.4rc5-cp310-cp310-musllinux_1_2_aarch64.whl

Download URL cybrentq-0.1.4rc5-cp310-cp310-musllinux_1_2_aarch64.whl
Size 215.7 kB
Tags CPython 3.10 Linux musl 1.2+ ARM64
SHA-256 checksum
How to use checksums
038499e037eeaea8d3a1f5cdfd0f804268f5daa2866774ca80c1da4ae8d31784
BLAKE2b-256 checksum
How to use checksums
2216bec7fd18992cbc24c46c16977e9f19e24021f7b8bc3357b8be3db29ca348
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.13

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 Aug 13, 2026.

Transparency log

Release files / cybrentq-0.1.4rc5-cp310-cp310-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl

Download URL cybrentq-0.1.4rc5-cp310-cp310-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Size 220.1 kB
Tags CPython 3.10 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
6be67629fbd347b905b9702ffa2ebdd8256c3477b566930f2f16190ab39ea533
BLAKE2b-256 checksum
How to use checksums
4aaff0566f18509ed8511a1df64169821ab7c2a4a326c87126b305520ca1bad1
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.13

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 Aug 13, 2026.

Transparency log

Release files / cybrentq-0.1.4rc5-cp310-cp310-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl

Download URL cybrentq-0.1.4rc5-cp310-cp310-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
Size 217.2 kB
Tags CPython 3.10 Linux glibc 2.17+ ARM64 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
86d47c832e53eff2893d7ed450eeda353cc7f3a846c130c92610acb841287678
BLAKE2b-256 checksum
How to use checksums
fa6f2d8eda4daee5ee6ed4ad081ce663b98a2f5ece896177f4eb07df206fbabe
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.13

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 Aug 13, 2026.

Transparency log

Release files / cybrentq-0.1.4rc5-cp310-cp310-macosx_11_0_arm64.whl

Download URL cybrentq-0.1.4rc5-cp310-cp310-macosx_11_0_arm64.whl
Size 107.5 kB
Tags CPython 3.10 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
043f6b48b1277ed7645a5e0e80c5e059c2d4cd9120fbac06aa2e36d96046a782
BLAKE2b-256 checksum
How to use checksums
d54a3d35fee6da18fcb69a3b991fc56327c1be5cf52aa1cdc59f60f0cd545686
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.13

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 Aug 13, 2026.

Transparency log

Release history Release notifications | RSS feed

0.1.5

31 release files

0.1.4

31 release files

This release

0.1.4rc5 This release

31 release files

0.1.3

31 release files

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