This release is a pre-release and may not be stable for production use.
tba-capability-client-registration
Layer-40 orchestration for the protocol-neutral lifecycle of a registered client.
Injected dependencies
Create, read, update, and disable callables are required and normally adapt layer-30 table operations. A durable audit callable is optional. Every collaborator may be synchronous or asynchronous.
Operations and readiness
Operations are register_client, get_registration, update_registration,
disable_registration, and optional record_audit_event. Readiness is true
only when all four lifecycle targets are bound; the report separately exposes
whether audit recording is available.
Protocol consumers
The layer-50 OAuth package maps RFC 7591/7592 behavior to this capability; OIDC uses that OAuth registration mapping where enabled.
Non-goals
This package does not parse HTTP, generate/hash secrets, validate OAuth metadata, select protocol errors, open storage sessions, or own registration state.
1 maintainer
Metadata
1 maintainer
Release files for tba-capability-client-registration 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_client_registration-0.4.0.dev2.tar.gz | 2.7 kB | Without provenance | Details for tba_capability_client_registration-0.4.0.dev2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| tba_capability_client_registration-0.4.0.dev2-py3-none-any.whl | Python 3 | none | any | Details for tba_capability_client_registration-0.4.0.dev2-py3-none-any.whl |
Total release size: 6.2 kB
Release files / tba_capability_client_registration-0.4.0.dev2.tar.gz
| Download URL | tba_capability_client_registration-0.4.0.dev2.tar.gz |
|---|---|
| Size | 2.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ef8d5eaad1ba8e3b5305efa539b672a273f11aaf86899450ab91e35e23ec0b76
|
|
BLAKE2b-256 checksum How to use checksums |
2a9b157a26f51858a69fb2fb8188051b6ddc89b5af9dbf95ba12ca3a965f7f74
|
| 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_client_registration-0.4.0.dev2-py3-none-any.whl
| Download URL | tba_capability_client_registration-0.4.0.dev2-py3-none-any.whl |
|---|---|
| Size | 3.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5f2385b5d804cb81b48ff4e5e19cfa9be7caabc016126eb537508ae3ea151231
|
|
BLAKE2b-256 checksum How to use checksums |
5c6e8ecc38391e2ff9cbcfa75bd9072151427635d56d3f1df87c66c5c2b05109
|
| 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-client-registration 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.
