This release is a pre-release and may not be stable for production use.
tba-capability-policy-evaluation
Layer-40 protocol-neutral composition for policy evaluation, batch evaluation, entity search, and effective policy-service description.
Injected dependencies
A policy evaluation callable is required. Entity search and service-description callables are optional. The targets are supplied by layer-10/20 implementations or layer-60 composition; this package does not construct an evaluator.
Operations and readiness
evaluate is required. evaluate_many is available as an order-preserving
composition of evaluate. search_entities and describe are optional and
are reported unavailable when their targets are not bound. Readiness follows
the required evaluation target.
Protocol consumers
The layer-50 AuthZEN package maps Authorization API 1.0 evaluation, batch, search, and PDP-metadata requirements to these operations. XACML adapters may consume the same normalized capability through their own versioned mappings.
Non-goals
This package does not parse AuthZEN or XACML messages, choose HTTP paths, authenticate callers, own policy state, open sessions, or implement a policy decision algorithm.
Metadata
Release files for tba-capability-policy-evaluation 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_policy_evaluation-0.4.0.dev2.tar.gz | 2.2 kB | Without provenance | Details for tba_capability_policy_evaluation-0.4.0.dev2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| tba_capability_policy_evaluation-0.4.0.dev2-py3-none-any.whl | Python 3 | none | any | Details for tba_capability_policy_evaluation-0.4.0.dev2-py3-none-any.whl |
Total release size: 5.4 kB
Release files / tba_capability_policy_evaluation-0.4.0.dev2.tar.gz
| Download URL | tba_capability_policy_evaluation-0.4.0.dev2.tar.gz |
|---|---|
| Size | 2.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a35bfde6751ed908cfdc124fc70b9fd668c94cf8753af2c1de4bbb0f14adc296
|
|
BLAKE2b-256 checksum How to use checksums |
9981b01aad5ee8a84520e32ea7c08ddecf7c84b62f7d2347436d1d321b6a0546
|
| 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_policy_evaluation-0.4.0.dev2-py3-none-any.whl
| Download URL | tba_capability_policy_evaluation-0.4.0.dev2-py3-none-any.whl |
|---|---|
| Size | 3.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
42b8624e370bfa833dcee2f73b2b31a8022c24f7a8caa26a6093087b5134dd99
|
|
BLAKE2b-256 checksum How to use checksums |
e6162aedd418304acf82079036aa7019f9ad3c86e7c3e1a6d54545227da0c840
|
| 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-policy-evaluation 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.