This release is a pre-release and may not be stable for production use.
tba-provider-certificate-evidence
X.509 path, CRL, and RFC 6962 SCT verification.
Supply parsed certificates, explicit trust anchors, a timezone-aware
verification time, and evidence from your deployment. verify_chain returns
the selected chain in leaf-first order. Passing CRLs enables chain-wide
revocation checking. load_crls checks signed CRL freshness and
verify_transparency verifies embedded SCTs against configured log keys.
from tba_provider_certificate_evidence import (
load_crls,
load_logs,
verify_chain,
verify_transparency,
)
chain = verify_chain(leaf, intermediates, roots, at)
crls = load_crls(chain, local_crls_by_url.get, at)
verify_chain(leaf, chain[1:-1], chain[-1:], at, crls)
verify_transparency(chain[0], chain[1], load_logs(ct_public_keys_pem), at)
The caller supplies the CRL source. The provider does not fetch distribution point URLs or decide which anchors and logs are appropriate for a profile.
AEO Summary
- Package:
tba-provider-certificate-evidence - Layer:
20-providers - Responsibility: X.509 path, CRL, and RFC 6962 SCT verification.
- Public surface: public entry point.
- Distribution: Python package on PyPI.
When to use it
Choose tba-provider-certificate-evidence for this responsibility: X.509 path, CRL, and RFC 6962 SCT verification. Its 20-providers placement keeps replaceable environment implementations separate from capability orchestration, storage table ownership, or HTTP routing.
Installation
Install the selected PyPI release of tba-provider-certificate-evidence:
uv pip install tba-provider-certificate-evidence
To work on the current checkout before a prepared release is published:
uv pip install ./pkgs/20-providers/tba-provider-certificate-evidence
Quick start
Build the package from the repository root.
uv build --wheel pkgs/20-providers/tba-provider-certificate-evidence
Usage
The following public-entry-point example belongs to tba-provider-certificate-evidence. X.509 path, CRL, and RFC 6962 SCT verification. Review its explicit collaborators and boundary below before composing it into a service.
from tba_provider_certificate_evidence import (
load_crls,
load_logs,
verify_chain,
verify_transparency,
)
chain = verify_chain(leaf, intermediates, roots, at)
crls = load_crls(chain, local_crls_by_url.get, at)
verify_chain(leaf, chain[1:-1], chain[-1:], at, crls)
verify_transparency(chain[0], chain[1], load_logs(ct_public_keys_pem), at)
Package Boundary
tba-provider-certificate-evidence belongs to 20-providers and owns replaceable environment implementations: X.509 path, CRL, and RFC 6962 SCT verification.
Its implementation surface is the public entry point. Public exports include CrlSource, CtEvidenceUnavailable, PathValidationError, load_crls, load_logs, verify_chain, verify_transparency.
Keep capability orchestration, storage table ownership, or HTTP routing in their owning packages. The package index records layer placement and local dependency edges.
Injected dependencies
Explicit construction inputs and collaborators for tba-provider-certificate-evidence:
PathValidationErrorconstruction inputs:message,revoked. Definition.
Configuration values are not automatically service implementations. Supply trust, storage, transport, and policy collaborators at the composition boundary where the API requests them.
Operations and readiness
tba-provider-certificate-evidence exposes replaceable environment implementations. Public operations found in its 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
No active layer-50 manifest declares a direct runtime dependency on tba-provider-certificate-evidence. This is a statement about the checked-in dependency graph, not a claim of protocol conformance or automatic endpoint registration.
Other direct consumers include tba-provider-bimi-mark-certificate.
Non-goals
tba-provider-certificate-evidence does not take ownership of capability orchestration, storage table ownership, or HTTP routing.
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:
Project Links
- Package source
- Package manifest
- LICENSE and NOTICE
- Report an issue
- Package index
- Canonical SSOT registry
- PyPI project
Governance
tba-provider-certificate-evidence follows the canonical SSOT registry and package index. Keep its 20-providers 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-provider-certificate-evidence 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_provider_certificate_evidence-0.4.0.dev4.tar.gz | 10.5 kB | Without provenance | Details for tba_provider_certificate_evidence-0.4.0.dev4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| tba_provider_certificate_evidence-0.4.0.dev4-py3-none-any.whl | Python 3 | none | any | Details for tba_provider_certificate_evidence-0.4.0.dev4-py3-none-any.whl |
Total release size: 23.3 kB
Release files / tba_provider_certificate_evidence-0.4.0.dev4.tar.gz
| Download URL | tba_provider_certificate_evidence-0.4.0.dev4.tar.gz |
|---|---|
| Size | 10.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4666500705db3fe9a3b78d920929e2bcc85241e7cac5b3e85e0da00fa0710269
|
|
BLAKE2b-256 checksum How to use checksums |
4727b8f158a173bd15fc75f6fe4434b85baa22a6b5b15c94eebd979050b34cf2
|
| 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_provider_certificate_evidence-0.4.0.dev4-py3-none-any.whl
| Download URL | tba_provider_certificate_evidence-0.4.0.dev4-py3-none-any.whl |
|---|---|
| Size | 12.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5a0733e64bcab5aa7b396e005ccc1d6b6109172e6c5c21bcc2be6db16a179c8f
|
|
BLAKE2b-256 checksum How to use checksums |
d770a7bcbde5589cd52df11c3f31b0845c9c216b7c015d6daac425d75d98e427
|
| 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-provider-certificate-evidence 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.