This release is a pre-release and may not be stable for production use.
tba-capability-token-revocation
Layer-40 orchestration for protocol-neutral durable token revocation.
Injected dependencies
A required revocation callable mutates durable token state; an optional audit callable records the lifecycle event. Both may be synchronous or asynchronous.
Operations and readiness
revoke_token is required and record_audit_event is optional. Readiness
follows the revocation binding, while the report separately exposes audit
availability.
Protocol consumers
The layer-50 OAuth package maps RFC 7009 behavior to this capability. Other protocol profiles reuse the normalized revocation result where applicable.
Non-goals
This package does not parse HTTP, authenticate callers, select RFC responses, open sessions, resolve token profiles, or own revocation storage.
1 maintainer
Metadata
1 maintainer
Release files for tba-capability-token-revocation 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_token_revocation-0.4.0.dev2.tar.gz | 2.1 kB | Without provenance | Details for tba_capability_token_revocation-0.4.0.dev2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| tba_capability_token_revocation-0.4.0.dev2-py3-none-any.whl | Python 3 | none | any | Details for tba_capability_token_revocation-0.4.0.dev2-py3-none-any.whl |
Total release size: 5.0 kB
Release files / tba_capability_token_revocation-0.4.0.dev2.tar.gz
| Download URL | tba_capability_token_revocation-0.4.0.dev2.tar.gz |
|---|---|
| Size | 2.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
10de0c0138f4316f30cf8a539215940edcf3ad26f49ab8a6709d134692ad8c72
|
|
BLAKE2b-256 checksum How to use checksums |
873052ada1f1ede7e4ce9a88949a7751671f8e3f9ad8a358bfd17b85e70a9b91
|
| 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_token_revocation-0.4.0.dev2-py3-none-any.whl
| Download URL | tba_capability_token_revocation-0.4.0.dev2-py3-none-any.whl |
|---|---|
| Size | 2.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2430e59a62838fa854df9567e3619ae2aab7ef95d9082395cadfea0a789113c8
|
|
BLAKE2b-256 checksum How to use checksums |
9fd6ff854fb0dcab2acb53c3446e95b04816c16d557e2103fab39cab429df541
|
| 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-token-revocation 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.
