This release is a pre-release and may not be stable for production use.
tigrbl-account-self-service
Layer-40 current-account profile, password, session, and consent orchestration.
Injected dependencies
The capability receives profile read/update, password change, session
list/revoke, consent list/revoke, and authorized-app revoke callables. Layer 60
normally adapts these callables to layer-30 table operations and hashing
providers. Every call is scoped by an authenticated AccountPrincipal.
Operations and readiness
All nine operations are required. Construction rejects missing or non-callable
delegates, and returned records are checked against the protocol-neutral layer-2
contracts. The effective operation set is reported as account.self-service
version 1.0.
Protocol consumers
This capability currently serves the layer-80 My Account HTTP carrier. A future versioned account protocol can map to the same operations without acquiring durable ownership.
Non-goals
This package owns no tables, sessions, HTTP objects, hashing provider, request authentication, or protocol binding.
1 maintainer
Metadata
1 maintainer
Release files for tba-capability-account-self-service 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_account_self_service-0.4.0.dev2.tar.gz | 2.5 kB | Without provenance | Details for tba_capability_account_self_service-0.4.0.dev2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| tba_capability_account_self_service-0.4.0.dev2-py3-none-any.whl | Python 3 | none | any | Details for tba_capability_account_self_service-0.4.0.dev2-py3-none-any.whl |
Total release size: 5.9 kB
Release files / tba_capability_account_self_service-0.4.0.dev2.tar.gz
| Download URL | tba_capability_account_self_service-0.4.0.dev2.tar.gz |
|---|---|
| Size | 2.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
11c7d37b75ff0fe167a8e4888a9b0eb7742eb23f18659a17eac9679bf4bb9fed
|
|
BLAKE2b-256 checksum How to use checksums |
3d5a2b6372332f91ea350fb54b321b75b930b40c7ff339d309487062755c7d53
|
| 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_account_self_service-0.4.0.dev2-py3-none-any.whl
| Download URL | tba_capability_account_self_service-0.4.0.dev2-py3-none-any.whl |
|---|---|
| Size | 3.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1b637d675c8757ae34938f34b29deaa19f58768a635a9f50f863e7ad0a190857
|
|
BLAKE2b-256 checksum How to use checksums |
a7933c69140f8da101f10eb67301bef3e8514ceb321e0ac98dc2bebb97d5ca58
|
| 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-account-self-service 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.
