Skip to main content

caurad — uvx / pip wrapper

Run the Caura broker from the Python ecosystem:

uvx caurad --help                        # package-name shorthand, kept working
uvx --from caurad caura --help           # run the canonical command directly
pipx install caurad && caura --help      # or install it

Interaction with the native installer

The PyPI wrapper and the native installer both provide a caura executable. If both are installed, your shell runs whichever appears first on PATH, and the two installations can be different versions. Use command -v caura to see which executable wins, type -a caura to list every match, and caura version to identify the selected version.

How it works

This package is a thin dispatcher — the broker itself is a single Go binary.

On first entry-point invocation, wrappers/uvx/caurad/cli.py detects your platform, downloads the matching signed archive from the public release mirror, verifies its SHA-256 against the published checksums.txt, caches the binary under ~/.cache/caura/<version>/, and os.execvs it with your arguments. The archive name is discovered from its platform suffix in checksums.txt, so release prefixes are not part of the wrapper contract. Both the caura and caurad package entries invoke the native payload as caura.

The install itself does NOT prefetch the binary — the download happens on first invocation. That keeps the package tiny and works under pipx / sandboxed installs where postinstall hooks don't fire.

The binary is downloaded from the public release mirror (https://caura.ai/caura/<tag>/) — the same source the wrappers/curl/install.sh installer uses, not this repo's GitHub Releases (which are private). SHA-256 verification is the integrity gate.

Environment overrides

  • CAURA_BINARY_BASE — base URL of a release mirror (default https://caura.ai/caura). Point it at an on-prem gateway's <origin>/caura to install from a private deployment.
  • CAURA_VERSION — pin a specific release tag instead of the installed package's version.

The published package version is set from the release tag by the PyPI-publish workflow; the 0.0.0 in pyproject.toml is a placeholder for local checkouts.

Licensed under Apache-2.0, matching the LICENSE at the repository root.

Metadata

Release files for caurad 0.13.4

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

Source distribution (sdist)

Source distribution for caurad 0.13.4
File Size Uploaded Provenance
caurad-0.13.4.tar.gz 8.1 kB With provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for caurad 0.13.4
File Interpreter ABI Platform
caurad-0.13.4-py3-none-any.whl Python 3 none any Details

Total release size: 14.6 kB

Release files / caurad-0.13.4.tar.gz

Download URL caurad-0.13.4.tar.gz
Size 8.1 kB
Tags Source
SHA-256 checksum
How to use checksums
966f5731406eba8ef9d7f92be56a6890134f59041e5eb6c901ed890ebe158cb4
BLAKE2b-256 checksum
How to use checksums
f155bc45ed0d5e728fce3b1f9d6d170bbe8e1a588dff142c490f9f6711c66090
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 Oct 9, 2026.

Transparency log

Release files / caurad-0.13.4-py3-none-any.whl

Download URL caurad-0.13.4-py3-none-any.whl
Size 6.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
6e3ad9f95ec5e34a78ed6b78b7f6a208f2a077c54d1e9054ed78f533cb2411ec
BLAKE2b-256 checksum
How to use checksums
86bed010a300c05841abb3aa31af55af9481a8ccd963d8077234bae8e13d3527
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 Oct 9, 2026.

Transparency log

Security for caurad 0.13.4

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

Select from 2 files

Attestation for caurad-0.13.4.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 9, 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.

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