Skip to main content

PyChrony: Python bindings for chrony NTP client

PyPI version Python versions CI Documentation License

Query your system's time synchronization status from Python. PyChrony provides bindings for chrony, the default NTP (Network Time Protocol) client on most Linux distributions, letting you monitor clock accuracy, sync status, and time sources programmatically.

Features

  • Read-only monitoring: Access tracking (offset, drift, stratum), sources (NTP servers, peers), statistics (samples, deviation), and RTC data
  • Pythonic API: Clean, typed interface following Python conventions
  • CFFI binding: Efficient interface to libchrony
  • Linux-first: Optimized for Linux environments with libchrony
  • Type hints: Full type annotation support for better IDE integration

Installation

pip install pychrony

Pre-built wheels include libchrony—no system dependencies needed. They cover Linux x86_64 and aarch64 (glibc and musl): one wheel for CPython 3.11 and later, plus free-threaded 3.14t and 3.15t. Python 3.10 installs from source.

Building from Source

Installing from source (the sdist, or any platform without a pre-built wheel) compiles the CFFI bindings, so it needs a C compiler, the libffi headers, and libchrony with its headers. libchrony is found through pkg-config; for a non-standard prefix, add <prefix>/lib/pkgconfig to PKG_CONFIG_PATH. A missing chrony.h or library stops the install with an error naming it.

To build from source even where a wheel exists:

pip install --no-binary pychrony pychrony

libchrony Package Availability

Distribution Available Install Command
Fedora 42+ ✅ Yes sudo dnf install libchrony-devel
RHEL/CentOS/Rocky/Alma 9 ✅ Yes (EPEL) sudo dnf install epel-release && sudo dnf install libchrony-devel
Debian/Ubuntu ❌ No Build from source (see below)
Alpine ❌ No Build from source (see below)
Arch Linux ❌ No Build from source (see below)

Building libchrony from Source

# Install build dependencies
# Debian/Ubuntu:
sudo apt-get install build-essential libtool-bin libffi-dev python3-dev

# Alpine:
sudo apk add gcc make libtool libffi-dev musl-dev

# Arch:
sudo pacman -S base-devel libtool libffi

# Clone and build libchrony
git clone https://gitlab.com/chrony/libchrony.git
cd libchrony
make
sudo make install prefix=/usr
sudo ldconfig

Development Install

git clone https://github.com/arunderwood/pychrony.git
cd pychrony
git submodule update --init
uv sync --all-groups

uv sync and uv pip install from the checkout install pychrony without the compiled bindings: [tool.uv] in pyproject.toml sets PYCHRONY_SKIP_CFFI=1, so development and the unit and contract tests need no libchrony. Connecting to chronyd from such an install raises ChronyLibraryError. Integration tests build the bindings in Docker (see TESTING.md).

With libchrony installed, PYCHRONY_BUILD_CFFI=1 uv sync or pip install -e . builds the bindings. With other installers, PYCHRONY_SKIP_CFFI=1 skips them.

Usage

from pychrony import ChronyConnection

with ChronyConnection() as conn:
    status = conn.get_tracking()
    print(f"Reference: {status.reference_id_name}")
    print(f"Stratum: {status.stratum}")
    print(f"Offset: {status.offset:.9f} seconds")
    print(f"Synchronized: {status.is_synchronized()}")

With no argument, pychrony tries chronyd's Unix socket and then its localhost command port, using the first that connects — the same candidates chronyc uses.

The two are not equivalent in privilege. The Unix socket is chronyd's control channel, restricted to the root or chrony user; the command port serves monitoring commands only, which is everything pychrony reads. Read-only consumers should prefer the command port, and can ask for it explicitly:

from pychrony import ChronyConnection

with ChronyConnection("127.0.0.1") as conn:
    status = conn.get_tracking()

Note that joining the chrony group does not grant access to the Unix socket. See Choosing a Transport for details.

Testing Your Code

pychrony.testing has factories that build pychrony objects with realistic defaults. They work in any test framework and do not need pytest:

from pychrony.testing import make_tracking

status = make_tracking(stratum=16, reference_id=0)
assert not status.is_synchronized()

pytest users can enable fixtures (chrony_tracking_status, chrony_source, chrony_source_stats, chrony_rtc_data) in their top-level conftest.py:

pytest_plugins = ["pychrony.pytest_plugin"]

The plugin is not loaded automatically, so installing pychrony adds no fixtures to other projects' test runs. See TESTING.md for details.

Compatibility

  • Python: 3.11, 3.12, 3.13, 3.14, 3.15
  • Platform: Linux (primary), other platforms where libchrony is available
  • chrony: 4.x and later

Resources

License

PyChrony is licensed under MIT. See LICENSE.

Pre-built wheels bundle libchrony which is licensed under LGPL-2.1-or-later. See LICENSES/LGPL-2.1-or-later.txt.

Metadata

Release files for pychrony 3.0.3

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

Source distribution (sdist)

Source distribution for pychrony 3.0.3
File Size Uploaded Provenance Actions
pychrony-3.0.3.tar.gz 84.9 kB With provenance Details for pychrony-3.0.3.tar.gz

Built distributions (wheels)

Table of built distributions (wheels) for pychrony 3.0.3
File Actions
pychrony-3.0.3-cp315-cp315t-musllinux_1_2_x86_64.whl CPython 3.15 CPython 3.15 free-threading Linux musl 1.2+ x86-64 Details for pychrony-3.0.3-cp315-cp315t-musllinux_1_2_x86_64.whl
pychrony-3.0.3-cp315-cp315t-musllinux_1_2_aarch64.whl CPython 3.15 CPython 3.15 free-threading Linux musl 1.2+ ARM64 Details for pychrony-3.0.3-cp315-cp315t-musllinux_1_2_aarch64.whl
pychrony-3.0.3-cp315-cp315t-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl CPython 3.15 CPython 3.15 free-threading Linux glibc 2.17+ ARM64, Linux glibc 2.28+ ARM64 Details for pychrony-3.0.3-cp315-cp315t-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
pychrony-3.0.3-cp315-cp315t-manylinux1_x86_64.manylinux_2_28_x86_64.manylinux_2_5_x86_64.whl CPython 3.15 CPython 3.15 free-threading Linux glibc 2.28+ x86-64, Linux glibc 2.5+ x86-64 Details for pychrony-3.0.3-cp315-cp315t-manylinux1_x86_64.manylinux_2_28_x86_64.manylinux_2_5_x86_64.whl
pychrony-3.0.3-cp314-cp314t-musllinux_1_2_x86_64.whl CPython 3.14 CPython 3.14 free-threading Linux musl 1.2+ x86-64 Details for pychrony-3.0.3-cp314-cp314t-musllinux_1_2_x86_64.whl
pychrony-3.0.3-cp314-cp314t-musllinux_1_2_aarch64.whl CPython 3.14 CPython 3.14 free-threading Linux musl 1.2+ ARM64 Details for pychrony-3.0.3-cp314-cp314t-musllinux_1_2_aarch64.whl
pychrony-3.0.3-cp314-cp314t-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl CPython 3.14 CPython 3.14 free-threading Linux glibc 2.28+ ARM64, Linux glibc 2.17+ ARM64 Details for pychrony-3.0.3-cp314-cp314t-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
pychrony-3.0.3-cp314-cp314t-manylinux1_x86_64.manylinux_2_28_x86_64.manylinux_2_5_x86_64.whl CPython 3.14 CPython 3.14 free-threading Linux glibc 2.5+ x86-64, Linux glibc 2.28+ x86-64 Details for pychrony-3.0.3-cp314-cp314t-manylinux1_x86_64.manylinux_2_28_x86_64.manylinux_2_5_x86_64.whl
pychrony-3.0.3-cp311-abi3-musllinux_1_2_x86_64.whl CPython 3.11 abi3 Linux musl 1.2+ x86-64 Details for pychrony-3.0.3-cp311-abi3-musllinux_1_2_x86_64.whl
pychrony-3.0.3-cp311-abi3-musllinux_1_2_aarch64.whl CPython 3.11 abi3 Linux musl 1.2+ ARM64 Details for pychrony-3.0.3-cp311-abi3-musllinux_1_2_aarch64.whl
pychrony-3.0.3-cp311-abi3-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl CPython 3.11 abi3 Linux glibc 2.17+ ARM64, Linux glibc 2.28+ ARM64 Details for pychrony-3.0.3-cp311-abi3-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
pychrony-3.0.3-cp311-abi3-manylinux1_x86_64.manylinux_2_28_x86_64.manylinux_2_5_x86_64.whl CPython 3.11 abi3 Linux glibc 2.28+ x86-64, Linux glibc 2.5+ x86-64 Details for pychrony-3.0.3-cp311-abi3-manylinux1_x86_64.manylinux_2_28_x86_64.manylinux_2_5_x86_64.whl

Total release size: 1.3 MB

Release files / pychrony-3.0.3.tar.gz

Download URL pychrony-3.0.3.tar.gz
Size 84.9 kB
Tags Source
SHA-256 checksum
How to use checksums
a88c11a7243314e3cb8a54747e09b648eb51ecceeca4e5cf0cc2c70d5a89c98e
BLAKE2b-256 checksum
How to use checksums
4d00b21ed8247847328d0d445322af5a640cc8b1a850e9e97415ae9f537e2941
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 Oct 31, 2026.

Transparency log

Release files / pychrony-3.0.3-cp315-cp315t-musllinux_1_2_x86_64.whl

Download URL pychrony-3.0.3-cp315-cp315t-musllinux_1_2_x86_64.whl
Size 96.1 kB
Tags CPython 3.15 CPython 3.15 free-threading Linux musl 1.2+ x86-64
SHA-256 checksum
How to use checksums
7b8b832127952073177e1a1ef9a2dbaabf8bbcbb23b0f307e3712b5ff9c6fcd2
BLAKE2b-256 checksum
How to use checksums
18456fd5f1cc57412c9cbc3b449c371f932321030357a9458df291ce5631789e
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 Oct 31, 2026.

Transparency log

Release files / pychrony-3.0.3-cp315-cp315t-musllinux_1_2_aarch64.whl

Download URL pychrony-3.0.3-cp315-cp315t-musllinux_1_2_aarch64.whl
Size 98.5 kB
Tags CPython 3.15 CPython 3.15 free-threading Linux musl 1.2+ ARM64
SHA-256 checksum
How to use checksums
bbc2a8f707d4e3128c82b8b2c9f0dfdb5906d41dfcead709d103a04e836dc010
BLAKE2b-256 checksum
How to use checksums
b106d9fb71333e0cb287e13de0649f204b5169355465b10dd6a04f56485a1ede
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 Oct 31, 2026.

Transparency log

Release files / pychrony-3.0.3-cp315-cp315t-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl

Download URL pychrony-3.0.3-cp315-cp315t-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
Size 101.4 kB
Tags CPython 3.15 CPython 3.15 free-threading Linux glibc 2.17+ ARM64 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
02551d581c2e39617eb057ebfa55c9c3e050c5bb7d6a4419f49fa795b2ce0a37
BLAKE2b-256 checksum
How to use checksums
c4b06a8561aef0bfeb7f8da9e8a739b51161888fc5e050a94056c9beeae7af21
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 Oct 31, 2026.

Transparency log

Release files / pychrony-3.0.3-cp315-cp315t-manylinux1_x86_64.manylinux_2_28_x86_64.manylinux_2_5_x86_64.whl

Download URL pychrony-3.0.3-cp315-cp315t-manylinux1_x86_64.manylinux_2_28_x86_64.manylinux_2_5_x86_64.whl
Size 98.5 kB
Tags CPython 3.15 CPython 3.15 free-threading Linux glibc 2.28+ x86-64 Linux glibc 2.5+ x86-64
SHA-256 checksum
How to use checksums
609bc4613dc89380f8401e51e1fa76cf4f1a996e1aff79654583362714c9ec92
BLAKE2b-256 checksum
How to use checksums
f29ec675b518b2016ca3d5148389b104673da6d2a0b669fdec93c0f6059ec826
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 Oct 31, 2026.

Transparency log

Release files / pychrony-3.0.3-cp314-cp314t-musllinux_1_2_x86_64.whl

Download URL pychrony-3.0.3-cp314-cp314t-musllinux_1_2_x86_64.whl
Size 102.0 kB
Tags CPython 3.14 CPython 3.14 free-threading Linux musl 1.2+ x86-64
SHA-256 checksum
How to use checksums
15ecc9b8dc68cfd75b739434ae46a48987053eb1a94dc6b1c4393161a3f49b89
BLAKE2b-256 checksum
How to use checksums
d78467feb72ea0219f5239fe0fa84e66d39928f623cba0aa55e9410ca086bf6b
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 Oct 31, 2026.

Transparency log

Release files / pychrony-3.0.3-cp314-cp314t-musllinux_1_2_aarch64.whl

Download URL pychrony-3.0.3-cp314-cp314t-musllinux_1_2_aarch64.whl
Size 104.6 kB
Tags CPython 3.14 CPython 3.14 free-threading Linux musl 1.2+ ARM64
SHA-256 checksum
How to use checksums
70e25935ebc4e80321198f7713793dcc1bdb13c13ac1c763adacb2fa3763dcbb
BLAKE2b-256 checksum
How to use checksums
42ac729d90d8f2580556f67ee2ddd0989f76f14b69e0ae5f5f1ee72b9a62b176
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 Oct 31, 2026.

Transparency log

Release files / pychrony-3.0.3-cp314-cp314t-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl

Download URL pychrony-3.0.3-cp314-cp314t-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
Size 108.3 kB
Tags CPython 3.14 CPython 3.14 free-threading Linux glibc 2.17+ ARM64 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
09b2de578eb50f13f272450f7bf4f5666ad92b82007c16867a06458409c4d3b1
BLAKE2b-256 checksum
How to use checksums
7603e88f59eca7d43f424a9ee0e03252961ba797036645178abb0a302e80da8d
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 Oct 31, 2026.

Transparency log

Release files / pychrony-3.0.3-cp314-cp314t-manylinux1_x86_64.manylinux_2_28_x86_64.manylinux_2_5_x86_64.whl

Download URL pychrony-3.0.3-cp314-cp314t-manylinux1_x86_64.manylinux_2_28_x86_64.manylinux_2_5_x86_64.whl
Size 104.2 kB
Tags CPython 3.14 CPython 3.14 free-threading Linux glibc 2.28+ x86-64 Linux glibc 2.5+ x86-64
SHA-256 checksum
How to use checksums
7db3f7f34f124e6e614388a865ea9ef6bbedf6fef74db7a0fbb6f6a604be1858
BLAKE2b-256 checksum
How to use checksums
3d804ccbf378e5e596bdf087a40f383ee54fe1c5ef80d296ca0cd68c452c8bc5
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 Oct 31, 2026.

Transparency log

Release files / pychrony-3.0.3-cp311-abi3-musllinux_1_2_x86_64.whl

Download URL pychrony-3.0.3-cp311-abi3-musllinux_1_2_x86_64.whl
Size 96.0 kB
Tags CPython 3.11 Linux musl 1.2+ x86-64 abi3
SHA-256 checksum
How to use checksums
c92eb884bf97739aab955e672503c365b42f1f16421ad04a778523603e6cd572
BLAKE2b-256 checksum
How to use checksums
46237dd5c7ca610c127eddb5ffcfcdf238a34b0a68c8243e77d16089aa8c8711
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 Oct 31, 2026.

Transparency log

Release files / pychrony-3.0.3-cp311-abi3-musllinux_1_2_aarch64.whl

Download URL pychrony-3.0.3-cp311-abi3-musllinux_1_2_aarch64.whl
Size 98.4 kB
Tags CPython 3.11 Linux musl 1.2+ ARM64 abi3
SHA-256 checksum
How to use checksums
95ea74db8f2366dbff01d964da4a7a7dacb7b09edb580c748cc5c807da36587c
BLAKE2b-256 checksum
How to use checksums
c34db496a12eef300845af74a9d091954c5407dec145df2dfe5e617b1f3e0358
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 Oct 31, 2026.

Transparency log

Release files / pychrony-3.0.3-cp311-abi3-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl

Download URL pychrony-3.0.3-cp311-abi3-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
Size 101.4 kB
Tags CPython 3.11 Linux glibc 2.17+ ARM64 Linux glibc 2.28+ ARM64 abi3
SHA-256 checksum
How to use checksums
cf44ce5708f5c8fde57ba59c16d0d74af9188b1bac011369ae101f38915e5957
BLAKE2b-256 checksum
How to use checksums
2c5a9dcd8b19e13f959036fc21fabce9bf8604a5bc2c8cea162ed69044534e9c
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 Oct 31, 2026.

Transparency log

Release files / pychrony-3.0.3-cp311-abi3-manylinux1_x86_64.manylinux_2_28_x86_64.manylinux_2_5_x86_64.whl

Download URL pychrony-3.0.3-cp311-abi3-manylinux1_x86_64.manylinux_2_28_x86_64.manylinux_2_5_x86_64.whl
Size 98.4 kB
Tags CPython 3.11 Linux glibc 2.28+ x86-64 Linux glibc 2.5+ x86-64 abi3
SHA-256 checksum
How to use checksums
7d3b2dce93e6d1b7cd8269e82802823c972b340193d0e8f68ce891f66d818eb3
BLAKE2b-256 checksum
How to use checksums
ef428247eb30e1b41129bbfa96eafbce59d5a9a9a6c009f5dfab1f75877996c3
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 Oct 31, 2026.

Transparency log

Security for pychrony 3.0.3

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 13 files in this release have been uploaded with provenance metadata.

Select from 13 files

Attestation for pychrony-3.0.3.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 Oct 31, 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