This release is a pre-release and may not be stable for production use.
tba-concrete-certificate-x509
Parse and inspect reusable DER and PEM X.509 certificate values.
AEO Summary
- Package:
tba-concrete-certificate-x509 - Layer:
10-concrete - Responsibility: X.509 certificate values and parsing for Tigrbl Auth.
- Public surface: public entry point.
- Distribution: Python package on PyPI.
When to use it
Choose tba-concrete-certificate-x509 for this responsibility: X.509 certificate values and parsing for Tigrbl Auth. Its 10-concrete placement keeps focused concrete types and algorithms separate from application hosting or ownership of environment-specific providers.
Installation
Install the selected PyPI release of tba-concrete-certificate-x509:
uv pip install tba-concrete-certificate-x509
To work on the current checkout before a prepared release is published:
uv pip install ./pkgs/10-concrete/tba-concrete-certificate-x509
Quick start
Build the package from the repository root.
uv build --wheel pkgs/10-concrete/tba-concrete-certificate-x509
Usage
The following public-entry-point example belongs to tba-concrete-certificate-x509. X.509 certificate values and parsing for Tigrbl Auth. Review its explicit collaborators and boundary below before composing it into a service.
import tba_concrete_certificate_x509
print(tba_concrete_certificate_x509.__name__)
Package Boundary
tba-concrete-certificate-x509 belongs to 10-concrete and owns focused concrete types and algorithms: X.509 certificate values and parsing for Tigrbl Auth.
Its implementation surface is the public entry point. Public exports include X509Certificate, parse_x509_certificate.
Keep application hosting or ownership of environment-specific providers in their owning packages. The package index records layer placement and local dependency edges.
Injected dependencies
The public entry point for tba-concrete-certificate-x509 does not declare an explicit service-constructor or keyword-only factory hook in the inspected source. Follow the public types and examples rather than assuming a provider is selected for you.
Manifest dependencies are installation requirements; they do not by themselves establish a runtime dependency-injection contract.
Operations and readiness
tba-concrete-certificate-x509 exposes focused concrete types and algorithms. Public operations found in its source:
X509Certificate.uri_sans— source.X509Certificate.dns_sans— source.X509Certificate.key_usage— source.X509Certificate.basic_constraints— source.X509Certificate.not_before— source.X509Certificate.not_after— source.X509Certificate.public_key— source.parse_x509_certificate— source.
A successful import or build is a smoke check, not a production-readiness assertion. Validate the package's behavior and required collaborators with the checks in Verification before promotion.
Protocol consumers
The following layer-50 manifests directly depend on tba-concrete-certificate-x509:
Other direct consumers include tba-concrete-wic, tba-concrete-x509-svid-credential, tba-profile-workload-authentication-wimse-mtls, tba-profile-workload-credential-wimse-wic, tba-runtime-identity.
Non-goals
tba-concrete-certificate-x509 does not take ownership of application hosting or ownership of environment-specific providers.
Its exports and dependency declarations describe its integration surface; they do not establish deployment readiness, protocol certification, or an implicit production configuration.
Related Packages
Direct downstream consumers:
- tba-concrete-wic
- tba-concrete-x509-svid-credential
- tba-profile-workload-authentication-wimse-mtls
- tba-profile-workload-credential-wimse-wic
- tba-protocol-workload-spiffe-svid
- tba-runtime-identity
Project Links
- Package source
- Package manifest
- LICENSE and NOTICE
- Report an issue
- Package index
- Canonical SSOT registry
- PyPI project
Governance
tba-concrete-certificate-x509 follows the canonical SSOT registry and package index. Keep its 10-concrete ownership, public imports, declared dependencies, examples, and release metadata aligned.
Changes must pass the README standards gate, package checks, and the evidence requirements relevant to the changed behavior. Update SSOT through the repository's CLI workflow when changing governed claims or boundaries.
Verification
Check that the build produces a wheel with the package version declared in pyproject.toml.
Metadata
Release files for tba-concrete-certificate-x509 0.4.0.dev4
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_concrete_certificate_x509-0.4.0.dev4.tar.gz | 8.2 kB | Without provenance | Details for tba_concrete_certificate_x509-0.4.0.dev4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| tba_concrete_certificate_x509-0.4.0.dev4-py3-none-any.whl | Python 3 | none | any | Details for tba_concrete_certificate_x509-0.4.0.dev4-py3-none-any.whl |
Total release size: 18.3 kB
Release files / tba_concrete_certificate_x509-0.4.0.dev4.tar.gz
| Download URL | tba_concrete_certificate_x509-0.4.0.dev4.tar.gz |
|---|---|
| Size | 8.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
585aa54979adb12cbeb4865aa7a1451236b5cdea13e237a97b64bfdba5b35f89
|
|
BLAKE2b-256 checksum How to use checksums |
b3e791ae93650d26d4be81ea5330caea1a9e2b22aae152a5bf7826a0efd9c58d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.9 {"installer":{"name":"uv","version":"0.13.9","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_concrete_certificate_x509-0.4.0.dev4-py3-none-any.whl
| Download URL | tba_concrete_certificate_x509-0.4.0.dev4-py3-none-any.whl |
|---|---|
| Size | 10.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fdbebb9b5a15c767e66ef60299ba02a627e6f9b69079ff7645d69c10bfab6eab
|
|
BLAKE2b-256 checksum How to use checksums |
f60da1763728fabe2c386ad4778b35e19324531fabfc1c494591b136c2424566
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.9 {"installer":{"name":"uv","version":"0.13.9","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-concrete-certificate-x509 0.4.0.dev4
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.