caurad — uvx / pip wrapper
Run the Caura broker from the Python ecosystem:
uvx caurad --help # run without installing
pipx install caurad && caurad --help # or install the canonical entry point
How it works
This package is a thin dispatcher — the broker itself is a single Go binary.
On first canonical or compatibility 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/memclawd/<version>/, and os.execvs it with your arguments —
so uvx caurad <args> behaves like the native memclaw <args>. Subsequent
invocations reuse the cached binary.
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://memclaw.net/memclaw/<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
Both are also read under their historical MEMCLAW_* spellings, which keep
working indefinitely; the CAURA_* name wins when it holds a non-empty value.
CAURA_BINARY_BASE— base URL of a release mirror (defaulthttps://memclaw.net/memclaw). Point it at an on-prem gateway's<origin>/memclawto 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.
Compatibility name
Existing pip install memclawd and uvx --from memclawd memclaw commands keep working through
the separate compatibility package, which depends on caurad. New installation
instructions should use the canonical name above.
Licensed under Apache-2.0, matching the LICENSE at the repository root.
1 maintainer
Metadata
1 maintainer
Release files for caurad 0.10.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| caurad-0.10.1.tar.gz | 5.9 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| caurad-0.10.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 12.6 kB
Release files / caurad-0.10.1.tar.gz
| Download URL | caurad-0.10.1.tar.gz |
|---|---|
| Size | 5.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9fe2d19331bcf00eecab7c6f1061a5fc95eaa470deb794d1c61e4e63cd882b7d
|
|
BLAKE2b-256 checksum How to use checksums |
5294dbe3b38698b0470b23be504ac29bcdf398856fbe79cb62c7578199ddb3e7
|
| 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 1, 2026.
Transparency logRelease files / caurad-0.10.1-py3-none-any.whl
| Download URL | caurad-0.10.1-py3-none-any.whl |
|---|---|
| Size | 6.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9c36a6f6df030173db9e02b944795512dd2d6ce6c5da836bc1b3869f1e8afe4e
|
|
BLAKE2b-256 checksum How to use checksums |
41b05d5335c6d3ba9c00f871ffcbb3d42a7065d34c630d0ba8c782562ccadfe9
|
| 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 1, 2026.
Transparency logSecurity for caurad 0.10.1
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.
Attestation for caurad-0.10.1.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 Sep 1, 2026.
Transparency logA 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.
