ratchet-authz-core
Framework-agnostic authorization broker core for Ratchet — an open-source implementation of the delegation-authorization broker described in arXiv:2609.00267 ("Delegation Without Trust"). A fully prompt-hijacked LLM agent still cannot exceed the authority explicitly delegated to it.
Implements workload identity, macaroon-style capability tokens, the
broker/PEP, hash-chained audit logging, and revocation. Zero
third-party runtime dependencies beyond the standard library and
cryptography (used only for Ed25519 workload identity keys).
Install
pip install ratchet-authz-core
For a specific agent framework, install the matching adapter instead (it
pulls in ratchet-authz-core automatically): ratchet-authz-langgraph,
ratchet-authz-crewai, ratchet-authz-autogen, or ratchet-authz-mcp.
Minimal usage
from ratchet_core import Broker, Ed25519WorkloadIdentity, tool_name_caveat
broker = Broker()
primary = Ed25519WorkloadIdentity("primary-agent")
token = broker.issue(
human_identity="alice@example.com",
primary_identity=primary,
caveats=[tool_name_caveat("read_calendar")],
)
decision = broker.authorize(
token,
presenting_identity=primary,
proposed_tool_call=..., # ratchet_core.ProposedToolCall
)
Full documentation, architecture diagram, and per-framework quickstarts: https://github.com/1manideep/ratchet
Metadata
Release files for ratchet-authz-core 0.1.0
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 | Actions |
|---|---|---|---|---|
| ratchet_authz_core-0.1.0.tar.gz | 21.6 kB | Without provenance | Details for ratchet_authz_core-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ratchet_authz_core-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for ratchet_authz_core-0.1.0-py3-none-any.whl |
Total release size: 40.2 kB
Release files / ratchet_authz_core-0.1.0.tar.gz
| Download URL | ratchet_authz_core-0.1.0.tar.gz |
|---|---|
| Size | 21.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
770611453b38d2ce4dd8dc7a6d2271501f2f4002de7d07420a688cb36577fea1
|
|
BLAKE2b-256 checksum How to use checksums |
a4c4ff5a4daf7bfee98e5355494834e05c3ca72d8f0e5f9003ef86cced386519
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.13.8 {"installer":{"name":"uv","version":"0.13.8","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / ratchet_authz_core-0.1.0-py3-none-any.whl
| Download URL | ratchet_authz_core-0.1.0-py3-none-any.whl |
|---|---|
| Size | 18.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b43f2985c86b6255fd505480f284166de83fd2e7171bbb5feaa1992765593a14
|
|
BLAKE2b-256 checksum How to use checksums |
57f700ec61af5cae40680680ad153d5aadac9aa56cfa6f2779d4de51dd8eb3dd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.13.8 {"installer":{"name":"uv","version":"0.13.8","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for ratchet-authz-core 0.1.0
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
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.