This release is a pre-release and may not be stable for production use.
tigrbl-grant-negotiation-capability
Layer-40 protocol-neutral composition for requesting, continuing, and rotating negotiated grants.
Injected dependencies
A grant-request target is required. Continuation and access-token rotation targets are optional. Layer-60 composition may build these targets from layer-20 key/token providers and the layer-30 GNAP grant-state operations.
Operations and readiness
request_grant is required. continue_grant and rotate_access_token are
optional and report unavailable when unbound. Readiness follows the required
request target; no grant or token state is retained in this package.
Protocol consumers
The layer-50 GNAP package maps RFC 9635 grant request, continuation, and token rotation semantics to these operations. Other grant-negotiation protocols may reuse the normalized contracts through their own mappings.
Non-goals
This package does not parse GNAP messages, validate key proofs, mint tokens, generate continuation secrets, open database sessions, or mount routes.
Metadata
Release files for tba-capability-delegated-access-negotiation 0.4.0.dev2
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 |
|---|---|---|---|---|
| tba_capability_delegated_access_negotiation-0.4.0.dev2.tar.gz | 2.2 kB | Without provenance | Details for tba_capability_delegated_access_negotiation-0.4.0.dev2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| tba_capability_delegated_access_negotiation-0.4.0.dev2-py3-none-any.whl | Python 3 | none | any | Details for tba_capability_delegated_access_negotiation-0.4.0.dev2-py3-none-any.whl |
Total release size: 5.4 kB
Release files / tba_capability_delegated_access_negotiation-0.4.0.dev2.tar.gz
| Download URL | tba_capability_delegated_access_negotiation-0.4.0.dev2.tar.gz |
|---|---|
| Size | 2.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
993c6063a1e1415a63a215824f431091b94fa6143688ac47dcfc0dbb3eeb4cf6
|
|
BLAKE2b-256 checksum How to use checksums |
208d60fdff734e43c1b86a32636d3a7d3f74d69cbc01bcfdc781031895890d6c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.7 {"installer":{"name":"uv","version":"0.13.7","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / tba_capability_delegated_access_negotiation-0.4.0.dev2-py3-none-any.whl
| Download URL | tba_capability_delegated_access_negotiation-0.4.0.dev2-py3-none-any.whl |
|---|---|
| Size | 3.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
be069eceed8df0e29414cdd3f023df67d41aa6d197df5cfe41c1983f1e1202f2
|
|
BLAKE2b-256 checksum How to use checksums |
dfcc5ae28b3fc4e8a3011a067fd82948936238cf761eb57340b9e7653266f7e3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.7 {"installer":{"name":"uv","version":"0.13.7","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for tba-capability-delegated-access-negotiation 0.4.0.dev2
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.